Skip to main content
Glama

stock_status

Curated UK stock, preorder and purchase-limit status for high-demand items. Hand-checked and cited, not live multi-shop scraping. 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": "stock_status"
  }
}

Input Schema

NameRequiredDescriptionDefault
idsNo
franchiseNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/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 disclose two important traits: the data is curated/hand-checked and cited (so possibly stale, not real-time) and each call costs $0.01 USDC via x402. It does not describe update cadence, what happens on an unknown id, or any payment/auth flow detail.

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 tight sentences with the core purpose front-loaded followed by provenance and pricing. No filler, though 'high-demand items' is vague enough that it does little work.

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?

Pricing and data provenance are covered, which is critical for an agent deciding whether to spend USDC. However, with an undefined 'ids' parameter and no output schema, the agent still lacks a clear picture of valid inputs and expected response shape.

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 the description adds nothing about either parameter. The 'franchise' enum values are self-explanatory, but 'ids' is entirely undefined — an agent cannot tell what identifier space it expects or whether it accepts a comma-separated list.

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?

States a specific resource and scope: curated UK stock, preorder and purchase-limit status for high-demand items. The clause 'Hand-checked and cited, not live multi-shop scraping' separates it from a live-scraping alternative, though no sibling is named explicitly.

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?

Usage is only implied — the description suggests this is for point-in-time, hand-verified status on specific items rather than broad restock feeds, but it never says when to prefer it over uk_restocks or drop_item. No prerequisites or exclusions beyond the negative comparison to scraping.

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