Skip to main content
Glama

Get an agent bot details

get_details_of_a_single_account_agent_bot
Read-onlyIdempotent

Get an agent bot details. Get the details of an agent bot in the account Requires feature: any of agent_bots, native_bots, voice_agents.

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": {
      "id": "<id>"
    },
    "name": "get_details_of_a_single_account_agent_bot"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesThe ID of the agentbot to be updated
fieldsNoOptional: return only these fields of each record.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered by structured data. The description adds one genuinely useful behavioral fact beyond that: the account feature requirement that gates the call. It says nothing about not-found behavior or error shapes, which keeps it at a moderate score.

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

Conciseness3/5

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

The first two sentences are near-duplicates ('Get an agent bot details.' / 'Get the details of an agent bot in the account'), which wastes the most prominent position. The feature requirement is correctly appended last, but the front-loaded redundancy costs it points.

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?

This is a simple two-parameter read tool with full schema coverage and complete annotations, so little is required. However, with no output schema, the description never indicates what 'details' are returned beyond the field names implied by the 'fields' enum, leaving the response shape under-described.

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%, so both 'id' and 'fields' are already documented in the schema, and the description adds no syntax or format detail beyond that. Baseline 3 applies; the description could have clarified that 'fields' projects the response, but the schema already carries that meaning.

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?

The description names a specific verb ('Get') and resource ('an agent bot in the account'), making it clearly a single-record retrieval, which distinguishes it in spirit from list_agent_bots. It stops short of naming any sibling explicitly, so differentiation relies on the tool name rather than the prose.

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 only usage-relevant content is the feature gate ('Requires feature: any of agent_bots, native_bots, voice_agents'), which tells the agent when the call will be permitted but not when to prefer this tool over list_agent_bots or get_inbox_agent_bot. The read-by-id intent is implied rather than stated.

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.

Resources