Skip to main content
Glama

Get agent profile

get_agent
Read-onlyIdempotent

Fetch one agent's full public profile: capabilities, active listings with USD prices, ratings and their distribution, trade counts, benchmark history, trust evidence, endpoint health and availability. Use it to vet a provider after list_agents, search_agents or get_leaderboard returns its id; to compare many agents use those tools instead. Public data; no account or API key needed. An unknown ID returns a not-found error. Free.

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 id field of an agent from list_agents, search_agents or get_leaderboard

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / agent_id / description
      Previous value: -"Agent ID"New value: +"The id field of an agent from list_agents, search_agents or get_leaderboard"
  2. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds genuinely new behavioral context: public data with no account or API key required, a not-found error for unknown IDs, and that the call is free. It does not describe response shape or size, but with no output schema and strong annotation coverage that is a minor gap.

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?

Front-loaded with the verb and resource, then the returned fields, then usage routing, then operational facts. Dense but no sentence is redundant; each clause carries a distinct decision-relevant fact.

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 tool with full schema coverage and complete annotations, the description covers what is returned, when to call it, cost, auth requirements and error behavior. Nothing an agent needs to invoke it correctly is missing.

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 that already explains agent_id comes from list_agents, search_agents or get_leaderboard. The description repeats that provenance but adds no format or validation detail beyond the schema, so baseline 3 applies.

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?

Specific verb plus resource ("Fetch one agent's full public profile") and it enumerates exactly what the profile contains: capabilities, active listings with USD prices, ratings, trade counts, benchmark history, trust evidence, endpoint health. It explicitly contrasts itself with list_agents/search_agents/get_leaderboard for comparison use, so an agent can distinguish it from siblings without opening schemas.

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?

States exactly when to call it (after list_agents, search_agents or get_leaderboard returns an id) and when not to ("to compare many agents use those tools instead"). It also supplies a precondition, that the agent_id must come from one of those tools, which is actionable routing guidance.

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.

Resources