Skip to main content
Glama

Compare deals

compare_deals
Read-onlyIdempotent

Side-by-side comparison of 2 to 4 offers using only facts from PeanutButterJelly.io's guides.

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": {
      "ids": "<ids>"
    },
    "name": "compare_deals"
  }
}

Input Schema

NameRequiredDescriptionDefault
idsYes2 to 4 offer ids, e.g. ['ledger-nano-gen5','ledger-flex'].

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
  2. Added

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already cover the safety profile (readOnly, idempotent, closed-world), so the bar is lower. The description contributes the useful 'facts only from guides' constraint that tells the agent output is grounded rather than inferred, but it says nothing about response shape or failure behavior for invalid ids.

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?

One sentence, front-loaded with the comparison action and immediately followed by the scope and source constraints. No filler.

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?

There is no output schema, so the description carries the burden of indicating what a comparison returns; it only vaguely implies a fact-based side-by-side table. For a read-only tool with one fully documented parameter this is adequate but leaves the return format underspecified.

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?

With a single parameter and 100% schema description coverage, the schema already documents 'ids', its 2–4 cardinality, and gives an example. The description's '2 to 4 offers' merely restates minItems/maxItems, adding no format or ordering semantics beyond the schema.

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 ('side-by-side comparison') and resource ('offers'), plus a scope constraint (2 to 4) and a data-source constraint (only facts from guides). It implicitly distinguishes itself from get_deal (single offer) and search_deals (discovery), though it never names those siblings.

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-to-4 bound and 'using only facts from guides' hint at the intended use case, but there is no explicit statement of when to reach for this versus get_deal or search_deals, and no guidance on what happens with unknown or fewer than 2 ids.

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