Skip to main content
Glama
Sign In

oracle

by com.dropwatchhq
OverviewDiscussionsAdmin

check_in_stock

Check whether a hobby item has recently dropped or restocked across the specialty shops we monitor for a niche. Returns recent in-stock matches (new + restock) with direct buy links. Use when an agent wants to find where a sold-out collectible is currently available.

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": {
      "niche": "<niche>",
      "query": "<query>"
    },
    "name": "check_in_stock"
  }
}

Input Schema

NameRequiredDescriptionDefault
nicheYesHobby niche: tcg, lego, funko, keebs, vinyl, aqua
queryYesProduct name to match against recent drops, e.g. 'Prismatic Evolutions' or 'Millennium Falcon'.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full burden. It discloses that it checks 'recent' drops/restocks and returns 'in-stock matches with direct buy links.' However, it does not specify the time window for 'recent,' which shops are monitored, or any limitations (e.g., regional availability). This leaves some behavioral ambiguity.

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?

The description is two sentences: the first states the action and result, the second provides the use case. It is front-loaded with key information, and every word adds value. Zero waste.

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?

The tool is simple with 2 parameters, both fully described. The return type is indicated ('recent in-stock matches with direct buy links'). No output schema exists, but the description sufficiently covers what the agent can expect. No further details are necessary for correct invocation.

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% with descriptions for both niche and query. The description adds practical examples ('Prismatic Evolutions', 'Millennium Falcon') that clarify the query format beyond the schema's generic 'Product name to match against recent drops.' This enhances usability.

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?

The description clearly states the tool checks for recent drops or restocks of a hobby item and returns matches with buy links. It distinguishes itself from sibling tools like check_recall (recalls) and find_settlements (settlements) by focusing on in-stock status for collectibles.

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

Usage Guidelines4/5

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

The description explicitly says 'Use when an agent wants to find where a sold-out collectible is currently available,' providing a clear usage context. However, it does not explicitly state when not to use it (e.g., for general price checks, which is covered by check_scalper_price), though the sibling list implies differentiation.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All oracle toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources