Skip to main content
Glama

list_agent_tools

Read-onlyIdempotent

Retrieve all resolved tools for an agent, covering API config, MCP, and core tools with resolved/error status to verify availability and troubleshoot configuration.

Instructions

All resolved tools (api_config + MCP + core), with resolved/error status

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "agent_id": "<agent_id>"
    },
    "name": "list_agent_tools"
  }
}

Input Schema

NameRequiredDescriptionDefault
agent_idYesAgent UUID

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv2.2.4
    • changedInput schema / properties / agent_id / description
      Previous value: -"UUID do agente"New value: +"Agent UUID"
  2. First observedv0.1.0

TDQS

C2.9/5.0
Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare readOnlyHint, idempotentHint, non-destructive and closed-world, so the safety profile is fully covered elsewhere. The description's one genuine contribution is disclosing that each entry carries `resolved`/`error` status and that results span api_config, MCP and core sources — useful, but it says nothing about per-agent scoping, empty results, or what a resolution failure means.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

One short clause, front-loaded with the scope detail, with no filler. It is a fragment rather than a sentence, but nothing is wasted.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple read-only list with full schema coverage and rich annotations, this is close to adequate, and there is no output schema requiring explanation. Still, with no output schema the description should clarify what a `resolved` vs `error` entry looks like and how the three source categories appear in the result.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100% with a single required `agent_id` UUID, so the schema does the work. The description never references agent_id or explains that results are scoped to that agent, adding no meaning beyond the schema; baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The fragment names the resource and its scope explicitly ("All resolved tools (api_config + MCP + core)") and adds the status dimension, so an agent can tell roughly what comes back. But it omits a verb and never distinguishes itself from siblings such as list_mcp_servers or list_agents, so the boundary is left to inference.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no statement of when to call this versus get_agent, list_mcp_servers, or list_agent_history, and no prerequisites or exclusions. The agent must infer usage from the name alone.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools