Skip to main content
Glama

Get one AI agent

agent_detail
Read-onlyIdempotent

One agent in full: its lead-capture settings, CRM sync state and whether it reached the runtime. The prompt and tool configuration are deliberately not returned — they are thousands of tokens of internal structure. Read only.

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": "agent_detail"
  }
}

Input Schema

NameRequiredDescriptionDefault
agent_idYesThe agent's id

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / agent_id / description
      Previous value: -"The agent's id, from agent_list"New value: +"The agent's id"
  2. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive), so the description's real contribution is scope disclosure: it names what comes back and explicitly declares that prompt and tool configuration are omitted to avoid thousands of tokens. That exclusion is genuinely useful information an agent cannot get from structured fields. It doesn't cover error behavior for an unknown id, which keeps it from a 5.

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

Conciseness5/5

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

Three tight sentences: payload scope front-loaded, exclusions second, safety note last. The justification for the exclusion ("thousands of tokens of internal structure") defensibly explains the omission rather than spending words.

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

Completeness4/5

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

With no output schema, the description carries return-value disclosure and does so by naming the three content areas plus the deliberately excluded ones. For a one-param fetch tool this is nearly complete; only failure modes for an invalid agent_id are unaddressed.

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?

There is a single required parameter with 100% schema coverage, so the schema already documents agent_id fully. The description adds no format, source, or lookup hints beyond confirming the tool works on one agent, which is the correct baseline for a fully covered single param.

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

Purpose4/5

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

"One agent in full" states a specific resource and singular scope, and names the domains of the payload (lead-capture settings, CRM sync state, runtime status). It doesn't explicitly name agent_list as the contrasting sibling, but the singular framing makes the distinction inferable.

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

Usage Guidelines3/5

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

The phrase "One agent in full" implies a fetch-by-id operation versus a listing, and "Read only" reinforces that this is a retrieval. There is no explicit when-to-use versus agent_list/agent_update guidance or prerequisite statement, so selection guidance is only implied.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.