Skip to main content
Glama

tcg_calendar

Official UK TCG set and product street dates with GBP RRP when published. Not shop stock. Costs $0.01 USDC (x402).

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": "tcg_calendar"
  }
}

Input Schema

NameRequiredDescriptionDefault
setNo
daysNo
kindNo
franchiseNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.1/5.0
Behavior3/5

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

With no annotations, the description carries the full burden, and it does add two useful behavioral facts: RRP is only present 'when published,' and each call costs $0.01 USDC via x402. It does not disclose what the response looks like, whether results are paginated, or what happens when no sets match the filters.

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?

Three short sentences, front-loaded with the core resource and immediately followed by the key exclusion and the cost caveat. Slightly telegraphic — the opening is a noun phrase with no verb — but nothing is wasted.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a four-parameter query tool with no annotations and no output schema, the definition is thin: it never says what a result record contains or how the filter parameters combine. The payment model is covered, but parameter behavior and return shape are not.

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

Parameters2/5

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

Schema description coverage is 0% and none of the four parameters (set, days, kind, franchise) are explained in the description. The enums for kind and franchise are self-describing, but 'days' (1-365) and 'set' are left ambiguous in both schema and prose — presumably a lookahead window, but the agent must guess.

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 first sentence names a specific resource and scope: official UK TCG set and product street dates, including GBP RRP where published. The clause 'Not shop stock' carves out a clear boundary from inventory-oriented siblings such as stock_status and uk_restocks. It lacks an explicit verb (list/lookup), but the retrieval intent is unambiguous.

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?

'Not shop stock' is a genuine exclusion directing the agent away from stock tools toward release-date data. However, no positive guidance is given about when to prefer this over upcoming_drops, next_drops, or drop_item, so the agent must infer the split from names alone.

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