Skip to main content
Glama

next_drops

Free: the next 3 UK collectibles drops across categories (Pokémon, One Piece, Lorcana, Yu-Gi-Oh!, Star Wars: Unlimited, MTG, LEGO, games including GTA 6). Includes dated releases and high-demand restock-watches still waiting for a confirmed UK day (e.g. a Pokémon Ultra-Premium Collection).

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.3/5.0
Behavior2/5

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

With no annotations, the description carries the full behavioral burden. It does disclose two useful traits: results are capped at 3, and the set mixes dated releases with undated 'restock-watches' awaiting a confirmed UK day. But it omits ordering/timeliness guarantees, what 'Free' actually limits, and what a drop entry contains, which matters for a tool returning heterogeneous records.

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?

A single sentence, front-loaded with the key constraint ('Free: the next 3 UK collectibles drops') before the category list. The long parenthetical enumerations (categories and the Ultra-Premium Collection example) are the only mild padding.

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

Completeness3/5

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

For a zero-parameter, read-only listing tool with no output schema, the description gives the scope, the cap, and a caveat about undated entries, which is a reasonable baseline. It still leaves the shape of a returned drop (fields, time ordering, how undated watches are flagged) unspecified in a case where no output schema fills that gap.

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?

The tool takes zero parameters, so there is nothing for the description to disambiguate and the baseline is 4. The schema is empty and fully covered.

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 concrete verb-less but specific resource: 'the next 3 UK collectibles drops' with an explicit cap and market scope, plus the product categories covered. It is clear what the tool returns, but it never distinguishes itself from the sibling 'upcoming_drops' or 'uk_restocks', which sound like overlapping capabilities.

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?

The leading 'Free:' signals a tiering model and implies this is the lightweight/convenience call, which gives some usage context. However, there is no explicit statement of when to choose this over 'upcoming_drops' or 'tcg_calendar', and no exclusion or prerequisite guidance.

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