get_agent
Get full agent profile by ID, including endorsements and reputation score.
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| agent_id | Yes | The agent ID (e.g., agt_E-PFtTAIQlfVleNm) |
agentstamp
Schema Changelog
Changes observed during successful MCP inspections. Dates show when Glama detected each change.
- First observed
TDQS
A3.9/5.0
Behavior3/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description carries the burden of disclosing behavior. It indicates a read operation and lists returned content (endorsements, reputation score), but does not mention potential errors, authentication requirements, or response format. This is adequate but not rich.
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 sentence that is direct and front-loaded. Every word contributes to explaining the tool's purpose and key outputs.
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 simple get-by-ID tool with one well-documented parameter and no output schema, the description sufficiently explains what the tool does and what it returns. No additional context is necessary.
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 description coverage is 100% for the single parameter, so the schema already documents agent_id well. The description only says 'by ID', adding no extra semantic detail beyond what the schema provides.
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 clearly states the verb 'Get' and the resource 'full agent profile by ID', and specifies that it includes endorsements and reputation score. This distinguishes it from siblings like get_agent_reputation and browse_agents.
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 is appropriate when the agent ID is known and a full profile is desired. However, it does not explicitly mention when to prefer this over alternatives like get_agent_reputation or search_agents.
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.3/5.0
Disambiguation3/5
Several tools overlap in purpose, such as bridge_erc8004_lookup and bridge_erc8004_trust_check, trust_check, get_agent, and get_agent_reputation all returning trust or reputation data. Descriptions help clarify the distinctions, but the similarities could lead an agent to select the wrong tool.
Naming Consistency3/5
Naming uses a mix of conventions: verb-noun (get_agent, search_agents), noun-first (compliance_report, dns_discovery), and prefix-based groupings (trust_*, bridge_*). While snake_case is consistent, the inconsistent verb/noun ordering and synonyms (lookup, check, verify) make it less predictable.
Tool Count4/5
With 19 tools, the set is slightly heavy but still justified by the platform's broad feature set covering trust checks, reputation, teams, wishes, compliance, and credentials. Some tools could be merged (e.g., bridge_erc8004_lookup and bridge_erc8004_trust_check), but the count is not excessive for the apparent scope.
Completeness3/5
The tool surface focuses heavily on reading and checking trust data, but lacks obvious lifecycle operations such as updating or deleting agents, creating wishes, or managing endorsements. The presence of create_team without corresponding team management (update/delete) leaves a notable gap.