Skip to main content
Glama

Compare gifts

compare
Read-onlyIdempotent

Use this to compare 2 to 5 collections ("Plush Pepe"), models ("Plush Pepe / Heart") or numbered gifts ("plushpepe-9998") by price estimate, rarity and supply in one call. An item that does not match is listed with suggestions. Do not use it for one item.

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": {
      "items": "<items>"
    },
    "name": "compare"
  }
}

Input Schema

NameRequiredDescriptionDefault
itemsYesNames to compare, for example ["Plush Pepe", "Heart Locket / Gold"].

Output Schema

NameRequiredDescriptionDefault
urlYes
noteYes
itemsYes
missingYes
cheapestNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already cover read-only, idempotent, non-destructive and closed-world, so the safety profile is settled. The description adds genuinely new behavior: unmatched items are returned with suggestions rather than failing the call, and results are keyed to price estimate, rarity and supply. It stops short of describing error behavior when all items fail or any rate limits.

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?

Three tight sentences: purpose and scope first, the accepted input forms second, the exclusion last. No redundant restatement of the title or the min/max limits beyond the useful mention of the range.

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?

With rich annotations, an output schema, and full schema description coverage, the remaining burden on the description is small and it is met: scope, input formats, and the partial-match behavior are all covered.

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

Parameters4/5

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

Schema coverage is 100% and there is only one parameter, so the baseline is high. The description still adds value by enumerating three accepted input formats, including the numbered-gift slug form ('plushpepe-9998') that the schema example does not show.

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?

States a specific verb (compare) plus the three resource types it accepts (collections, models, numbered gifts) and the three dimensions compared (price estimate, rarity, supply). This clearly distinguishes it from the get_* siblings that fetch a single entity.

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

Usage Guidelines4/5

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

Gives an explicit range constraint ('2 to 5') and an explicit exclusion ('Do not use it for one item'), which covers the main misuse case. It does not name the single-item alternative (get_collection/get_gift), so the routing is implied rather than spelled out.

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