Skip to main content
Glama

Get Single Agent Security & Runtime Dossier

get_agent_dossier
Read-onlyIdempotent

Retrieve the complete 4-point Virginia Scout runtime heartbeat audit, measured RTT latency, 64-bit MGLE-NNP coupler breakdown, and SHA-256 tool-schema hash for one exact agent_id. Use only when inspecting a known agent_id; use search_agent_directory if you need to find the agent_id first.

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

Input Schema

NameRequiredDescriptionDefault
agent_idYesExact agent or MCP server identifier from the Radial Switchboard phonebook (e.g. 'mcp://...' or registry slug).

Output Schema

NameRequiredDescriptionDefault
foundYesTrue when agent_id exists in the audited phonebook.
dossierNoFull runtime audit record, coupler code, and schema hash.
agent_idYesRequested agent identifier.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / agent_id / description
      Previous value: -"Unique agent or MCP server identifier from the Radial Switchboard phonebook (for example 'mcp://...' or registry slug)."New value: +"Exact agent or MCP server identifier from the Radial Switchboard phonebook (e.g. 'mcp://...' or registry slug)."
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "properties": {
      +    "agent_id": {
      +      "description": "Requested agent identifier.",
      +      "type": "string"
      +    },
      +    "dossier": {
      +      "description": "Full runtime audit record, coupler code, and schema hash.",
      +      "type": "object"
      +    },
      +    "found": {
      +      "description": "True when agent_id exists in the audited phonebook.",
      +      "type": "boolean"
      +    }
      +  },
      +  "required": [
      +    "found",
      +    "agent_id"
      +  ],
      +  "type": "object"
      +}
  2. Changed1 schema field changed
    • addedInput schema / properties / agent_id / description
      Added value: +"Unique agent or MCP server identifier from the Radial Switchboard phonebook (for example 'mcp://...' or registry slug)."
  3. First observed

TDQS

A4.3/5.0
Behavior3/5

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

The annotations already declare this is read-only, idempotent, non-destructive, and not open-world, so the safety profile is covered. The description adds useful lookup scoping by emphasizing 'one exact agent_id' and restricting use to known IDs, but it does not say what happens when the ID is unknown or whether the audit data is live versus cached. With annotations and an output schema carrying much of the burden, a 3 is appropriate.

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?

Two sentences, both front-loaded: the first specifies the returned audit artifacts, and the second gives the routing rule to the sibling tool. The dense terminology is purposeful rather than wasteful, and no sentence could be removed without losing selection-relevant information.

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 single-parameter, read-only lookup with a 100%-covered schema, rich annotations, and an output schema, the description supplies everything an agent needs to select and invoke it correctly. It names the exact-ID constraint and the alternative search tool, and the output schema handles return-value documentation.

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 schema already explains that agent_id is an exact identifier from the Radial Switchboard phonebook, including example formats. The description adds only the word 'exact' and otherwise repeats what the schema provides, so the baseline of 3 is correct.

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?

The description uses a specific verb ('Retrieve') and enumerates the exact artifacts returned for a single agent: the 4-point runtime heartbeat audit, measured RTT latency, MGLE-NNP coupler breakdown, and SHA-256 tool-schema hash. It explicitly distinguishes itself from search_agent_directory, so an agent can tell which tool performs the exact-ID lookup without opening either 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?

It states a clear positive condition ('Use only when inspecting a known agent_id') and names the alternative for the opposite case ('use search_agent_directory if you need to find the agent_id first'). No inference is required to choose between this tool and its sibling.

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.