Skip to main content
Glama

get_prices_batch

Use this for any question that needs prices for more than about 10 trading cards at once, up to 50. For a few cards, call get_prices (free) per card instead of this $0.05 batch. Each card includes raw_nm, raw_pc, and graded prices when stored, and one successful call has one charge. $0.05 per success, limited to 30 per minute.

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": {
      "card_ids": "<card_ids>"
    },
    "name": "get_prices_batch"
  }
}

Input Schema

NameRequiredDescriptionDefault
card_idsYesUp to 50 catalog card UUIDs

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "additionalProperties": true,
      +  "description": "Prices in USD with numeric price_usd, currency, source, as_of, and stale.",
      +  "type": "object"
      +}
  2. First observed

TDQS

A4.7/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does well: it discloses per-call cost ($0.05 per success), the billing unit (one successful call = one charge), and a rate limit (30/minute). It also names the returned price fields (raw_nm, raw_pc, graded prices when stored). The only residual gap is behavior on partially invalid or unknown card_ids, which is not addressed.

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, front-loaded with the decision rule (batch size) before the cost and limit details. Nothing is padded; the price is restated once, but the second mention defines the billing unit rather than repeating the comparison.

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?

For a one-parameter batch tool, the description covers selection criteria, cost, rate limit, and return fields, and an output schema exists so return values need no further explanation. An agent has everything needed to decide and call correctly.

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%, so the single card_ids parameter is already documented, establishing a baseline of 3. The description adds practical meaning beyond the schema by implying a sensible minimum batch size (>10) for this tool, which affects how an agent fills the array.

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 (batch price retrieval for trading cards) plus a precise scope: more than ~10 and up to 50 cards. It explicitly contrasts itself with the sibling get_prices, so an agent can distinguish the two without inspecting either schema.

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 use condition (>10 cards, max 50), an explicit not-use condition (a few cards), and names the cheaper alternative get_prices per card. The cost tradeoff ($0.05 vs free) makes the routing decision concrete rather than implied.

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