Skip to main content
Glama

compare_tools

Read-onlyIdempotent

The six-criteria comparison matrix for two listings, side by side.

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": {
      "a": "<a>",
      "b": "<b>"
    },
    "name": "compare_tools"
  }
}

Input Schema

NameRequiredDescriptionDefault
aYesFirst listing slug.
bYesSecond listing slug.

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 this a read-only, idempotent, non-destructive, closed-world call, so the safety profile is covered. The description adds one genuinely useful behavioral fact beyond that — the result is a six-criteria matrix for exactly two listings, side by side — but says nothing about what happens with invalid or mismatched slugs, or whether the response is a table, object, or text.

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?

A single short sentence with no filler, and the key information (two listings, six criteria, side-by-side output) is front-loaded. It is arguably under-specified rather than padded, which is penalized in contextual completeness rather than here.

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 two-parameter read-only tool with full schema coverage and rich annotations, the description supplies the core output concept. However, with no output schema, an agent still cannot predict the return shape of the 'six-criteria matrix' or which criteria are involved, and there is no hint of failure behavior for unknown slugs.

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 coverage is 100%, so both parameters ('a' and 'b') are already documented as listing slugs, and the description's 'two listings, side by side' merely confirms that reading. It adds no syntax details such as whether slugs are case-sensitive or whether parameter order affects the matrix orientation.

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 states the concrete deliverable — a six-criteria comparison matrix across two listings — which usefully corrects the tool name's implication that 'tools' rather than listings are compared. It is a noun phrase describing output rather than a verb+resource action, and it does not distinguish this from fetching two listings via get_listing or search_listings.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no when-to-use guidance at all: no statement of the scenario that should trigger a side-by-side comparison rather than two get_listing calls, and no preconditions such as both listings needing to exist or be comparable. The agent must infer the use case entirely from the noun phrase.

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