Skip to main content
Glama

Compare agents

compare_agents
Read-only

Side-by-side facts for 2 or 3 agents by slug.

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": {
      "slugs": "<slugs>"
    },
    "name": "compare_agents"
  }
}

Input Schema

NameRequiredDescriptionDefault
slugsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered structurally. The description adds only that results are comparative ('side-by-side'), without saying what 'facts' are returned, whether missing slugs error out or are skipped, or how the comparison is ordered or presented.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

One short sentence, front-loaded with the operation and scope, with no filler. It is efficient, though the terseness leaves gaps that a clause or two could have closed.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

This is a simple one-parameter read tool with annotations and no output schema, so the description needn't explain return values in detail. Still, with no output schema present, the phrase 'facts' is the only signal about what comes back, leaving the response shape underspecified for a comparison tool.

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 0%, so the single 'slugs' array parameter is undocumented in the schema. The description partially compensates by clarifying that entries are agent slugs and that 2-3 must be supplied, which explains the minItems/maxItems bounds, but it does not say what a slug looks like or how invalid ones are handled.

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 names a specific operation and resource ('Side-by-side facts for 2 or 3 agents') and constrains the scope to slug-based lookup, so an agent can tell this is a multi-agent comparison rather than a single lookup. It stops short of naming or contrasting the siblings search_agents and get_agent, so differentiation is left to inference.

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 '2 or 3 agents' framing implies the comparison use case and implicitly contrasts with a single-agent fetch, but there is no explicit when-to-use statement, no exclusion ('do not use for one agent'), and no mention of the sibling tools. Usage is implied rather than stated.

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