Skip to main content
Glama

Get agent

get_agent
Read-onlyIdempotent

Full current state: genome, cognitive graph (nodes/edges with weights and trust), and summary counts.

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

Input Schema

NameRequiredDescriptionDefault
agent_idYesThe developmental agent's id, from create_agent.

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / agent_id / description
      Added value: +"The developmental agent's id, from create_agent."
  2. First observed

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, closed-world and non-destructive behavior, so the safety profile is fully covered without the description. The description adds that the read returns the complete state rather than a filtered subset, but says nothing about payload size, staleness, or failure behavior for an unknown agent_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?

It is a single short sentence with zero padding, and the substantive content - the returned data - leads immediately. The only flaw is the verbless fragment style, which makes the first read slightly abrupt.

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 one fully documented parameter, complete annotations, and an output schema that carries the return structure, this tool is simple enough that a one-line content summary suffices. What remains missing is routing guidance against describe_agent, which is a usage gap more than a completeness one.

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 parameter with 100% schema description coverage ('The developmental agent's id, from create_agent'), so the schema already carries the semantics. The description adds no additional meaning about the identifier, which is the expected baseline when schema coverage is complete.

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 the specific resource content returned: the genome, the cognitive graph with nodes/edges carrying weights and trust, and summary counts, qualified as 'full current state'. That is clearer than a bare restatement of the name, though it omits a leading verb and does not distinguish itself from the sibling describe_agent.

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 explicit when-to-use statement and no when-not. The phrase 'full current state' weakly implies this is the comprehensive read versus a lighter sibling like describe_agent, but the agent is left to infer that comparison on its own.

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.