get_agent
Get agent details by ID
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| agent_id | Yes |
Joy Trust Network
Schema Changelog
Changes observed during successful MCP inspections. Dates show when Glama detected each change.
- First observed
TDQS
A3.5/5.0
Behavior2/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description bears full responsibility for disclosing behavior. It only states 'Get' which restates the tool name, adding no information about side effects, error handling, or output format. This is a minimal disclosure.
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?
The description is a single, six-word sentence that is direct and free of any filler. It conveys the essential information without unnecessary 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?
Given the tool's simplicity (one parameter, no output schema), the description covers the core action and input fairly well. It could mention what 'details' entail, but for a simple getter this is acceptable and matches the minimal scope.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Parameters4/5
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The schema only defines 'agent_id' as a string, but the description clarifies it is used as an identifier ('by ID'). This adds meaning beyond the raw schema, compensating for the 0% schema description coverage.
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 clearly states the tool's purpose: 'Get agent details by ID' with a specific verb and resource. It does not explicitly differentiate from sibling tools like 'discover_agents' or 'get_ticket', but the subject 'agent details' is distinct enough.
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 'by ID' implies this tool is for retrieving a single agent when an ID is known, contrasting with listing tools like 'discover_agents'. However, there is no explicit when-to-use or alternative guidance, leaving the context to be inferred.
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.
TDQS
B3.2/5.0
Disambiguation4/5
Most tools target distinct resources and actions. The only potential confusion is between approve_job and complete_deal, both releasing payments, but descriptions clearly differentiate job vs deal contexts. Overall, tools are well-separated.
Naming Consistency4/5
Almost all tools follow a consistent verb_noun pattern (create_, get_, list_, etc.). The only outlier is network_stats, which lacks a verb, but this is a minor deviation from an otherwise uniform convention.
Tool Count2/5
With 29 tools, the set exceeds the 25-tool threshold for a well-scoped server. While the platform covers many domains (jobs, payments, trust, identity, campaigns, tickets), the high count feels heavy and could benefit from consolidation or clearer separation into sub-modules.
Completeness3/5
Core job and stake lifecycles are fully covered, but tickets and campaigns only support create/list/get with no update, delete, or close operations. Payment also lacks a direct send/unified transfer option. These gaps are notable but workarounds exist via deals and top-up links.