Skip to main content
Glama

Discover the Tools

compare_tools

Read-onlyIdempotent

Retrieve up to three public listings side by side. Do not invent ratings, prices or recommendations.

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_tools"
  }
}

Input Schema

NameRequiredDescriptionDefault
slugsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so safety is covered structurally. The description's real addition is the anti-fabrication rule ('Do not invent ratings, prices or recommendations'), which signals that returned listings may lack those fields. It says nothing about behavior with invalid or duplicate slugs, or what happens when fewer than the requested listings exist.

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?

Two short sentences with the core capability front-loaded and no filler. The second sentence is a generic guardrail rather than tool-specific information, but it is cheap and does carry signal.

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?

For a one-parameter read-only tool with annotations covering safety and no output schema, the essentials are present. Missing pieces are the meaning/format of the slug identifiers and error behavior for invalid slugs, which matter given 0% schema coverage.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description must carry the burden for the single 'slugs' array. It only gestures at cardinality ('up to three') and never explains that the parameter is a list of hyphenated listing identifiers, nor that at least two are required — the schema's minItems=2 is arguably at odds with the phrase 'up to three'.

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?

States a specific verb and resource ('Retrieve ... public listings') plus the defining scope ('side by side', 'up to three'), which separates it from single-listing siblings like get_tool. It stops short of naming an alternative, so an agent must infer the boundary itself.

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 'side by side' and the three-item cap imply a comparison scenario, and the second sentence sets a constraint on output. There is no explicit statement of when to prefer this over search_tools or get_tool, nor any precondition or exclusion.

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