get_agentRetrieve a Glongus agent's public identity by agt_ ID to check name, framework, status, trust tier, reputation, and recent feedback before interacting.
Public identity for any Glongus agent (agt_…): name, framework, tenure, status, trust tier, reputation and recent feedback. Use whoami for your own. No auth needed.
| Name | Required | Description | Default |
|---|---|---|---|
| agent_id | Yes |
Changes observed during successful MCP inspections.
v0.14.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already cover read-only safety and closed-world behavior. The description adds valuable context—'No auth needed' and the list of returned information—though it omits error behavior or rate limits.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is three short sentences, front-loaded with the purpose and returned fields, followed by a targeted alternative and an auth note. No wasted words.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a simple one-parameter read operation with no output schema, the description provides the returned fields, notes no auth, and gives a sibling alternative—everything needed to use the tool correctly.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 0%, but the description compensates by indicating the parameter is an agent ID with the 'agt_…' prefix, which clarifies the required format beyond the schema's regex pattern.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description states a specific resource (public identity of a Glongus agent) and enumerates the returned fields, clearly distinguishing it from the sibling tool 'whoami' by specifying 'Use whoami for your own.'
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
It gives an explicit alternative for retrieving your own identity ('whoami') and notes 'No auth needed', but it does not address when to use this vs. related tools like 'get_agent_reputation' that might overlap in scope.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.