Tool Catalog
A Kindo agent acts through tools. This catalog lists the tools an agent can be granted: the 123 integrations Kindo ships, the 2,368 tools they expose, and the built-in tools that need no integration at all.
Which of these an agent can actually call is set per agent and per user group. See Tool Action Access Controls for how access is scoped, and Integrations Setup for how connections are configured.
How tools are named
Section titled “How tools are named”Once an integration is connected, each of its tools is exposed to the agent under a fully qualified name: the integration prefix, an underscore, then the tool name. The GitHub integration’s list_pull_requests tool reaches the agent as github_list_pull_requests. The catalog pages list these fully qualified names.
An integration can be connected in more than one way. Microsoft Entra ID, for example, offers delegated OAuth, application credentials, and GCC High variants of each. Each variant is a separate connection with its own credentials, which is why 123 integrations yield 159 connectable entries.
The prefix comes from the connection, not from the integration, so each variant prefixes its tools with its own identifier. Jira Data Center’s tools arrive as jira-data-center-basic_*, not jira_*. The catalog lists each integration’s tools once, under its primary connection’s prefix; if you connect through another variant, expect that variant’s prefix on the same tool names.
Platform tools follow the same rule under the platform prefix, so get_conversation reaches the agent as platform_get_conversation. Most built-in tools carry no prefix at all: the agent sees file_read and shell_exec. The exception is platform_search_docs, which is a built-in despite the prefix — it is listed with the built-ins below, not with the platform tools. The kindo_-prefixed spellings below are the request-side type values used by the Responses API, not the names an agent, transcript, or approval card shows.
Integrations by category
Section titled “Integrations by category”Built-in tools
Section titled “Built-in tools”These tools need no integration. Granting one in an agent’s configuration is necessary but not sufficient: almost every built-in also depends on how your deployment is set up, so read the Requires column alongside the tool.
| Tool | Responses API type | Description | Requires |
|---|---|---|---|
library_list | — | List the files in the Kindo file library, with the content IDs the download tools take. | Nothing further |
shell_exec | kindo_shell | Run a shell command in the agent’s sandbox. | A configured sandbox provider |
file_read | kindo_file_read | Read a file in the sandbox workspace. | A configured sandbox provider |
file_write | kindo_file_write | Write a file in the sandbox workspace. | A configured sandbox provider |
file_list | kindo_file_list | List the workspace’s files. | A configured sandbox provider |
web_download | kindo_web_download | Download a URL into the workspace. | A configured sandbox provider |
files_download_original | kindo_files_download_original | Fetch an uploaded file in its original form. | A configured sandbox provider |
files_download_as_text | kindo_files_download_as_text | Fetch an uploaded file converted to text. | A configured sandbox provider |
file_share_with_user | kindo_file_share_with_user | Hand a workspace file back to the user. | A configured sandbox provider |
browser_control | kindo_browser_control | Drive a headless browser session. | A sandbox provider, and browser automation enabled for the org |
browser_screenshot | kindo_browser_screenshot | Capture the browser viewport. | A sandbox provider, and browser automation enabled for the org |
browser_list_network_requests | kindo_browser_list_network_requests | List the requests the page made. | A sandbox provider, and browser automation enabled for the org |
browser_export_request_as_curl | kindo_browser_export_request_as_curl | Export one captured request as curl. | A sandbox provider, and browser automation enabled for the org |
mint_upload_url | — | Mint a short-lived signed upload URL for the integration tools that write files. | A sandbox provider, and the preview enabled for your organization by Kindo |
search | kindo_web_search | Search the web. | Web search enabled for the org |
knowledge_store_search | kindo_knowledge_store_search | Search the org’s knowledge store. | Knowledge Store enabled, with documents attached to the conversation |
vpn_connect | kindo_vpn_connect | Attach the sandbox to a customer network. | Kindo-hosted deployments, with VPN tools enabled for the org |
vpn_disconnect | kindo_vpn_disconnect | Detach the sandbox from that network. | Kindo-hosted deployments, with VPN tools enabled for the org |
dashboard_generate | kindo_dashboard_generate | Build a dashboard from the run’s data. | Experimental; Kindo-hosted orgs with Canvas dashboards enabled |
dashboard_update | kindo_dashboard_update | Revise a dashboard already generated. | Experimental; Kindo-hosted orgs with Canvas dashboards enabled |
platform_search_docs | — | Search Kindo’s documentation for product and platform guidance. | Kindo docs search enabled for the deployment, and not a whitelabeled deployment |
Platform tools
Section titled “Platform tools”Tools an agent uses to read and drive Kindo itself, rather than an external system. Unlike the built-ins above, these arrive together when the Platform server is selected.
| Tool | Description |
|---|---|
platform_get_conversation | Read a conversation’s messages and tool calls. |
platform_get_agent_run | Read one agent run’s status and output. |
platform_list_agents | List the agents the caller can see. |
platform_view_agent_configuration | Read an agent’s configuration summary, or use section and cursor for paged exact text and resource IDs. |
platform_list_agent_runs | List an agent’s runs. |
platform_start_standalone_agent_run | Start an agent run. |
platform_create_agent | Create a prompt-based agent with optional model and initial tool servers, returning a saved configuration snapshot. |
platform_edit_agent | Change an agent’s name, description, instructions, or model and return a saved configuration snapshot. |
platform_set_agent_tool_server | Enable or disable a whole tool server on an agent. Account connections and tool approval settings still govern execution. |
platform_set_agent_skill | Attach or detach an existing accessible skill by lineage ID. Requires Skills to be enabled. |
platform_set_agent_knowledge_content | Attach or remove existing accessible knowledge content. Requires Knowledge Store to be enabled; attachment may start indexing. |
platform_list_agent_configuration_options | List accessible model or tool server IDs, with pagination. |
platform_list_departments | List active departments and member counts, newest first, with pagination. |
platform_create_department | Create a department and return its ID. |
platform_rename_department | Rename an active department by ID. |
platform_archive_department | Archive a department and clear it from every current member. |
platform_list_users | List organization members with roles, departments, and bounded user-group summaries. |
platform_get_user | Look up one organization member by user ID or email. |
platform_set_user_departments | Preview or apply up to 100 department assignments, reporting rejected rows separately. |
Platform tools require Platform MCP to be enabled and configured for your
organization. Skill and knowledge attachment also require the SKILLS and
KNOWLEDGE_STORE feature flags respectively. Agent-level model selection requires
the Agent Builder Instructions beta (AGENT_BUILDER_INSTRUCTIONS); while it is
disabled, a model can be saved on the agent but does not override the request’s
model at execution. Contact Kindo to request beta access.
Department and member-directory tools require organization-admin access. Department tools have limited access on Kindo-hosted deployments and are not available on self-managed deployments. Contact Kindo to request access; your organization’s plan must also include department management. Directory reads remain available without those department-specific requirements. Discovery omits directory and department tools when their requirements are not met. Calls recheck current access, including when you use a previously discovered tool.
Use department and user IDs for assignments. Display values over 255 characters
end in …; group lists contain at most 50 entries and report truncation.
For bulk assignment, call with dry_run: true to preview, then dry_run: false
to apply. Omitting dry_run applies changes. The first assignment for a user
wins; invalid rows are rejected without blocking valid rows. Changes commit
by department, so a failure can leave part of a batch applied. If the result
is unavailable, inspect current departments and users before retrying.
Archiving clears all current members and cannot be reversed through these tools.