Skip to main content
Glama

Scalper Price Checker

by com.dropwatchhq

price_check

Check whether a price for a collectible is FAIR / OVER / SCALPED vs the current retail median across the shops we poll. Returns the retail min/max/median, the number of shops carrying it, the price multiple, and a verdict. Use this to decide if a listing is overpriced before buying. niche must be one of: tcg (Pokémon & TCG), lego (LEGO sets), funko (Funko Pop), keebs (Mechanical keyboards), vinyl (Vinyl records), aqua (Aquarium livestock).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nicheYesNiche key, e.g. 'tcg', 'lego', 'funko', 'keebs', 'vinyl', 'aqua'.
priceNoOptional: the price you are seeing. If given, the verdict compares against it.
queryYesProduct name to look up, e.g. 'Charizard V' or 'LEGO 10307'.

TDQS

A4.4/5.0
Behavior4/5

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

No annotations provided, so description carries full burden. Describes return values (retail min/max/median, shops count, price multiple, verdict). Omits potential data freshness or rate limits, but overall transparent.

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?

Two concise sentences plus a list of niches. No superfluous words. Information is front-loaded.

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?

With no output schema, description adequately covers behavior and return values. Could detail exact field names but sufficient for an agent to understand usage.

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%, baseline 3. Description adds value by explaining 'price' parameter is optional and used for comparison, and lists all valid niche values.

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 a price against retail median and returns a verdict (FAIR/OVER/SCALPED) with supporting stats. It distinguishes itself from sibling list_niches by focusing on price evaluation.

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?

Explicitly says 'Use this to decide if a listing is overpriced before buying,' providing clear context. Does not specify when not to use or alternatives, but sibling is different enough.

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

All Scalper Price Checker toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.4/5.0
Disambiguation5/5

The two tools have completely distinct purposes: list_niches provides valid niche options, and price_check uses those options to check prices. There is no overlap or ambiguity.

Naming Consistency5/5

Both tools follow a consistent verb_noun pattern with underscores: list_niches and price_check. The naming is clear and predictable.

Tool Count3/5

With only 2 tools, the server feels quite thin for a service covering multiple niches. While it may be sufficient for a simple price checker, the limited tool count suggests a minimal surface area.

Completeness4/5

Within its stated purpose of checking prices for collectible niches, the server provides a complete workflow: list niches then check a price. No obvious gaps are present, though a tool to compare multiple items could be a minor addition.

Resources