Skip to main content
Glama

Get agent

get_agent
Read-onlyIdempotent

Everything the registry knows about one listed agent, by the id search_agents returned: its endpoints (MCP and/or A2A), every tool with its input schema and whether it is free, priced (with the price) or needs a key, uptime, latency and reputation from paid work. Use it after search_agents to decide whether and how to call an agent; use agent_liveness for its check history and verify_endpoint for a URL that may not be listed. Read-only, no account. Returns one JSON record.

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_agent"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesThe listing id search_agents returned, e.g. 866e8de4b31f45c0

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / id / description
      Added value: +"The listing id search_agents returned, e.g. 866e8de4b31f45c0"
  2. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint/idempotent/non-destructive, but the description adds genuinely new behavioral facts: no account required, one JSON record returned, and the specific payload contents (endpoints, per-tool input schemas, free/priced/key-required status, uptime, latency, reputation). With no output schema, this return-content disclosure is the main value-add; it stops short of noting errors, rate limits, or behavior for an unknown id.

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?

Front-loaded with the resource, then payload contents, then routing guidance — no filler sentences. The parenthetical payload enumeration is dense but each item is decision-relevant; only the redundant 'Read-only' clause slightly duplicates the annotations.

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

Completeness5/5

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

For a one-parameter lookup with no output schema, the description covers what is returned, what auth is needed, when to reach for it versus siblings, and the return shape (single JSON record). Nothing an agent needs in order to call it correctly is missing.

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 coverage is 100% and the single parameter already carries a description naming the source (search_agents) and an example format. The description restates that provenance without adding syntax, validation, or failure semantics, so the schema does the heavy lifting.

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

Purpose5/5

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

States a specific retrieval verb and resource ('Everything the registry knows about one listed agent'), and immediately scopes it to the id produced by search_agents. An agent can distinguish it from search_agents, agent_liveness and verify_endpoint without opening any schema.

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

Usage Guidelines5/5

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

Explicit sequencing ('Use it after search_agents to decide whether and how to call an agent') plus two named alternatives with the condition that selects each: agent_liveness for check history, verify_endpoint for an unlisted URL. When-to-use and when-to-use-something-else are both covered.

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.