F
license-
qualityC
maintenanceLook up Old School RuneScape Grand Exchange prices in real-time using the official OSRS Wiki Prices API, no API key required.
Scalper Price Checker
Server Details
Check if a collectible's price is FAIR/OVER/SCALPED vs the current retail median across shops.
- Status
- Healthy
- Last Tested
- Transport
- Streamable HTTP
- URL
Glama MCP Gateway
Connect through Glama MCP Gateway for full control over tool access and complete visibility into every call.
MCP client
Glama
MCP server
Full call logging
Every tool call is logged with complete inputs and outputs, so you can debug issues and audit what your agents are doing.
Tool access control
Enable or disable individual tools per connector, so you decide what your agents can and cannot do.
Managed credentials
Glama handles OAuth flows, token storage, and automatic rotation, so credentials never expire on your clients.
Usage analytics
See which tools your agents call, how often, and when, so you can understand usage patterns and catch anomalies.
100% free. Your data is private.
Tool Definition Quality
A4.4/5.0
Tool DescriptionsA
Average 4.4/5 across 2 of 2 tools scored.
Server CoherenceA
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.
Available Tools
2 toolslist_nichesAInspect
List the collectible niches this price checker covers (TCG, LEGO, Funko, keyboards, vinyl, aquarium). Use first to pick a valid 'niche' value for price_check.
ParametersJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
No parameters | |||
Tool Definition Quality
A4.4/5.0
Behavior4/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description bears full burden. It states that the tool lists niches, implying a non-destructive, read-only query. The description is clear but could explicitly note that it does not modify any state or require authentication.
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 long, front-loaded with the action and examples. Every word serves a purpose, with no unnecessary information.
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?
For a simple list tool with no output schema, the description adequately conveys its purpose and usage. It does not specify the return format (e.g., a JSON array), but the agent can reasonably infer that it returns a list of niche names. This is sufficient given the tool's simplicity.
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 has no parameters, and schema coverage is 100%. The description adds value by listing example niches and explaining the tool's purpose, meeting the baseline expectation for zero-parameter tools.
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 that the tool lists collectible niches covered by the price checker, with specific examples (TCG, LEGO, Funko, keyboards, vinyl, aquarium). It distinguishes itself from the sibling tool price_check by explaining its role as a prerequisite for selecting a niche.
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 tells when to use the tool: 'Use first to pick a valid 'niche' value for price_check.' This provides clear context and usage order, though it could mention that it is a read-only operation with no side effects.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
price_checkAInspect
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).
ParametersJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| niche | Yes | Niche key, e.g. 'tcg', 'lego', 'funko', 'keebs', 'vinyl', 'aqua'. | |
| price | No | Optional: the price you are seeing. If given, the verdict compares against it. | |
| query | Yes | Product name to look up, e.g. 'Charizard V' or 'LEGO 10307'. |
Tool Definition Quality
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.
Claim this connector by publishing a /.well-known/glama.json file on your server's domain with the following structure:
{
"$schema": "https://glama.ai/mcp/schemas/connector.json",
"maintainers": [{ "email": "your-email@example.com" }]
}The email address must match the email associated with your Glama account. Once published, Glama will automatically detect and verify the file within a few minutes.
Control your server's listing on Glama, including description and metadata
Access analytics and receive server usage reports
Get monitoring and health status updates for your server
Feature your server to boost visibility and reach more users
For users:
Full audit trail – every tool call is logged with inputs and outputs for compliance and debugging
Granular tool control – enable or disable individual tools per connector to limit what your AI agents can do
Centralized credential management – store and rotate API keys and OAuth tokens in one place
Change alerts – get notified when a connector changes its schema, adds or removes tools, or updates tool definitions, so nothing breaks silently
For server owners:
Proven adoption – public usage metrics on your listing show real-world traction and build trust with prospective users
Tool-level analytics – see which tools are being used most, helping you prioritize development and documentation
Direct user feedback – users can report issues and suggest improvements through the listing, giving you a channel you would not have otherwise
The connector status is unhealthy when Glama is unable to successfully connect to the server. This can happen for several reasons:
The server is experiencing an outage
The URL of the server is wrong
Credentials required to access the server are missing or invalid
If you are the owner of this MCP connector and would like to make modifications to the listing, including providing test credentials for accessing the server, please contact support@glama.ai.
Discussions
No comments yet. Be the first to start the discussion!
Related MCP Servers
- AlicenseAqualityCmaintenanceSearch eBay and get real price data, straight from an AI agent.3MIT
- AlicenseAqualityBmaintenanceLets Claude compare Magic: The Gathering single-card prices across six Czech online card shops, with optional Cardmarket fallback. Queries all shops in parallel and returns a normalized, price-sorted list.102MIT
- Flicense-qualityBmaintenanceEnables AI agents to search Mandarake auctions and Suruga-ya for used hobby items, and compare prices between the two platforms in real time.