Skip to main content
Glama

upcoming_drops

Upcoming UK drops with dates, GBP prices and cited links: TCGs, LEGO, official video game launches including GTA 6, sale windows, prereleases and restock watches. Filter by franchise, kind or channel. 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": "upcoming_drops"
  }
}

Input Schema

NameRequiredDescriptionDefault
daysNo
kindNo
channelNo
franchiseNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior3/5

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

With no annotations at all, the description carries the full burden, and it does disclose the single most important behavioral fact: the call costs $0.01 USDC via x402, which an agent must know before invoking. It also hints at the returned fields (dates, GBP prices, cited links). It says nothing about rate limits, failure modes, whether prices are always present for unannounced items, or pagination.

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?

Two compact sentences plus a cost note, front-loaded with the resource and scope. The enumerated content types are dense but each adds discriminating detail; the only wasted space is the parenthetical example 'including GTA 6'.

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

Completeness4/5

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

Given no output schema and no annotations, the description covers the essentials: what is returned (dates, GBP prices, cited links), how to narrow it (three filter axes) and the payment cost. The notable gap is the undocumented days parameter and the absence of any default window or sort order, which matters for a date-based listing tool.

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 description coverage is 0%, so the description should compensate. It names three of the four parameters (franchise, kind, channel) and frames them as filters, which matches their enum names, but adds no meaning beyond the enum values already visible in the schema. The fourth parameter, days, is never mentioned, so the agent gets no guidance on the lookahead window at all.

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 description names a specific resource and scope: upcoming UK drops, with enumerated content types (TCGs, LEGO, video game launches, sale windows, prereleases, restock watches) and sample return fields. It never distinguishes itself from overlapping siblings such as next_drops, uk_restocks or tcg_calendar, so an agent cannot route between them from the text alone.

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

Usage Guidelines2/5

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

'Filter by franchise, kind or channel' is parameter guidance rather than usage guidance. There is no statement of when to prefer this tool over next_drops or uk_restocks, no when-not guidance, and no note on default behavior when no filters are supplied.

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