Skip to main content
Glama

Sealed product prices

sealed_prices
Read-onlyIdempotent

Use this when the user asks about sealed product prices in one game: booster boxes, elite trainer boxes, bundles, packs, tins and cases. Returns today's market price (USD) and 30-day percent change per product, most expensive first. For one named product, search_cards plus card_price is more direct.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "sealed_prices"
  }
}

Input Schema

NameRequiredDescriptionDefault
gameNoCard game, one of: pokemon, one-piece, lorcana, riftbound, yugioh, gundam, fusion-world.pokemon
limitNo1 to 300.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / game / description
      Previous value: -"Card game, one of: pokemon, one-piece, lorcana, riftbound, yugioh, gundam."New value: +"Card game, one of: pokemon, one-piece, lorcana, riftbound, yugioh, gundam, fusion-world."
    • changedInput schema / properties / game / enum
      Previous value: -[
      -  "pokemon",
      -  "one-piece",
      -  "lorcana",
      -  "riftbound",
      -  "yugioh",
      -  "gundam"
      -]New value: +[
      +  "pokemon",
      +  "one-piece",
      +  "lorcana",
      +  "riftbound",
      +  "yugioh",
      +  "gundam",
      +  "fusion-world"
      +]
  2. Changed3 schema fields changed
    • addedInput schema / properties / game / description
      Added value: +"Card game, one of: pokemon, one-piece, lorcana, riftbound, yugioh, gundam."
    • addedInput schema / properties / game / enum
      Added value: +[
      +  "pokemon",
      +  "one-piece",
      +  "lorcana",
      +  "riftbound",
      +  "yugioh",
      +  "gundam"
      +]
    • addedInput schema / properties / limit / description
      Added value: +"1 to 300."
  3. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, and closed-world, so the safety profile is covered. The description adds return semantics not in the annotations: USD market price, 30-day percent change, and 'most expensive first' ordering, which tells the agent what the result set looks like.

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 sentences, no filler: trigger first, return payload and ordering second, alternative tool last. Every sentence carries distinct information.

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?

An output schema exists, annotations are rich, and both parameters are fully documented in the schema, so the description does not need to re-explain returns or safety. What remains — scope, ordering, and sibling routing — is all present.

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% with the game enum fully enumerated and the limit range documented, so the schema carries the parameter burden. The description only adds that the game parameter scopes results to a single game; it says nothing about the limit or pagination behavior.

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 and resource ('sealed product prices in one game') and enumerates the product classes covered (booster boxes, ETBs, bundles, packs, tins, cases), which is exactly the distinction needed against card-level siblings like card_price and graded_price.

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

Usage Guidelines5/5

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

Gives an explicit trigger ('when the user asks about sealed product prices in one game') and names the alternative for a different case: 'For one named product, search_cards plus card_price is more direct.' That is a real when/when-not routing rule.

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