Tools - Qoder

Tools determine what an Agent can do. By configuring the tools field when creating or updating an Agent, you precisely control its capabilities.

What tools do

When executing a task, the Agent decides which capabilities it can call based on the tools configuration. Built-in tools are configured through { "type": "agent_toolset_20260401", "enabled_tools": [...] }, selectively enabling atomic tools in the enabled_tools array. Client-side custom tools are configured as separate { "type": "custom", ... } entries. When enabled_tools is a non-empty allowlist, tools outside the list are not visible to the model and no invocation attempt is made. When enabled_tools is omitted or an empty array, all built-in tools are exposed to the model. When the tools field itself is omitted or set to [], the model receives no tool schema at all (see FAQ below).

Available tools

Tool name (enabled_tools value)	Purpose	Typical use cases
`Bash`	Shell command execution	Installing dependencies, running scripts, calling APIs with curl
`Read`	File reading	Viewing mounted files, code reading
`Write`	File writing (create/overwrite)	Generating reports, producing output
`Edit`	Partial file editing	Changing configuration, editing code
`Glob`	Glob pattern file listing	Finding code files
`Grep`	File content search	Locating strings
`WebFetch`	HTTP GET a single page	Fetching documentation/pages
`WebSearch`	Web search	Looking up information
`DeliverArtifacts`	Deliver files the Agent produced under `/data/` to the user as downloadable artifacts. Emits `agent.artifact_delivered` events.	When the user asks for a file/report/export as a deliverable

Notes:

Tool names must use the exact values in the table, and event streams use the same values
Omitting enabled_tools or passing an empty array [] enables all built-in tools (including DeliverArtifacts listed above). If you want the Agent to have no tools at all, omit the whole tools field or set it to [].
When enabled_tools is a non-empty allowlist, only the listed tools are visible to the model. To use DeliverArtifacts alongside a custom allowlist, you must include it explicitly (e.g. ["Bash", "Write", "DeliverArtifacts"]).
Each tool name in enabled_tools is validated — writing an unknown name (e.g. "Foo") returns 400: "unknown tool name 'Foo'"
Built-in and MCP tool permissions are configured with configs[].permission_policy; see Permission Policies.
The old per-tool-object schema (such as {"type": "bash_20250124"}) is no longer supported

Current format: single object

Built-in tool configuration uses a single object that toggles specific tools via the enabled_tools array:

{
  "tools": [
    {
      "type": "agent_toolset_20260401",
      "enabled_tools": ["Bash", "Read", "Write", "Edit", "Glob", "Grep", "WebFetch", "WebSearch"]
    }
  ]
}

Set when creating an Agent:

curl -X POST https://api.qoder.com/api/v1/cloud/agents \
  -H "Authorization: Bearer $QODER_PAT" \
  -H "Content-Type: application/json" \
  -d '{
    "name": "dev-agent",
    "model": "ultimate",
    "system": "You are a development assistant",
    "tools": [
      {
        "type": "agent_toolset_20260401",
        "enabled_tools": ["Bash", "Read", "Write", "Edit", "Glob", "Grep", "WebFetch", "WebSearch"]
      }
    ]
  }'

Custom client-side tools

Custom tools let your application expose actions that the Agent can request but the platform does not execute directly. When the Agent calls a custom tool, the session pauses with a requires_action stop reason. Your client executes the tool and sends the result back with a user.custom_tool_result event.

{
  "tools": [
    {
      "type": "agent_toolset_20260401",
      "enabled_tools": ["Read", "Write"]
    },
    {
      "type": "custom",
      "name": "lookup_order",
      "description": "Look up an order by ID.",
      "input_schema": {
        "type": "object",
        "properties": {
          "order_id": {"type": "string"}
        },
        "required": ["order_id"]
      }
    }
  ]
}

Custom tool rules:

name, description, and input_schema are required.
input_schema must be a JSON Schema object with "type": "object".
Custom tool names are case-insensitively unique within the Agent.
A custom tool name must not collide with a built-in tool name such as Bash or Read.
Names starting with mcp__ are reserved for MCP tools.
permission_policy is not supported on custom tools because the client executes them.

See Send an event for the user.custom_tool_result response flow.

Configuration examples

Minimal (CLI only)
Full development stack

{
  "tools": [
    {
      "type": "agent_toolset_20260401",
      "enabled_tools": ["Bash"]
    }
  ]
}

{
  "tools": [
    {
      "type": "agent_toolset_20260401",
      "enabled_tools": ["Bash", "Read", "Write", "Edit", "Glob", "Grep", "WebFetch", "WebSearch"]
    }
  ]
}

Create a new version (PUT full replacement)

Use PUT to create a new version of the Agent with updated tool configuration:

curl -X PUT https://api.qoder.com/api/v1/cloud/agents/agent_abc123 \
  -H "Authorization: Bearer $QODER_PAT" \
  -H "Content-Type: application/json" \
  -d '{
    "version": 1,
    "tools": [
      {
        "type": "agent_toolset_20260401",
        "enabled_tools": ["Bash", "Read", "Write", "Edit"]
      }
    ]
  }'

PUT is a full replacement (not a patch) — fields not included will be cleared. You must include the version field for optimistic concurrency control:

If the supplied version matches the current version: 200, version increments by 1
If the supplied version is stale: 409 { error: { type: "conflict_error", message: "Version conflict. Expected version N, got M." }}

Existing Sessions are unaffected; new Sessions use the updated configuration.

Inspect current tool configuration

curl https://api.qoder.com/api/v1/cloud/agents/agent_abc123 \
  -H "Authorization: Bearer $QODER_PAT" | jq '.tools'

Example output:

[
  {
    "type": "agent_toolset_20260401",
    "enabled_tools": ["Bash", "Read", "Write", "Edit", "Glob", "Grep", "WebFetch", "WebSearch"]
  }
]

FAQ

Q: What if I don’t configure tools? A: The Agent has no tools available and can only have plain-text conversations. To give the Agent any tool capability, pass at least [{"type":"agent_toolset_20260401"}] (which enables all built-in tools). Q: Can I override tools at the Session level? A: Not currently. Tool configuration is bound to the Agent, and all Sessions for that Agent share the same toolset. Q: Does the order of tools matter? A: No. The Agent decides which tool to invoke based on the task context. Q: Will the version suffix change over time? A: Yes. As new tool versions ship, new dated suffixes are introduced. Watch the changelog and adopt the latest suffix.

Next steps

Permission policies

Control which tool calls run, ask, or deny.

Agent Skills

Attach domain expertise to your agent.

Start a session

Run an agent against an environment.

Agent setup

Review Agent configuration.

​What tools do

​Available tools

​Current format: single object

​Custom client-side tools

​Configuration examples

​Create a new version (PUT full replacement)

​Inspect current tool configuration

​FAQ

​Next steps