rangeview-mcp

Check price and stock

check_availability

Look up price and stock availability for up to 20 products at once using identifiers such as ID, SKU, or name.

Instructions

Bulk price/stock lookup for up to 20 products by id, SKU, or name. Use when tracking specific items rather than browsing.

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": {
      "identifiers": "<identifiers>"
    },
    "name": "check_availability"
  }
}

Input Schema

Name	Required	Description	Default
`identifiers`	Yes	Product ids, SKUs, or names (max 20)

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Jul 28, 2026

TDQS

A4/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 full burden. It states a read operation (lookup) and limits to 20 items, but does not disclose error handling, response format, or authentication requirements. This is adequate for a simple lookup but lacks depth.

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 with no extraneous words. It efficiently conveys the function and usage guidance, earning its place without redundancy.

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?

No output schema exists, so the description omits return value details. For a bulk lookup, mentioning what the response contains (e.g., mapping of identifiers to price/stock) would improve completeness. Still, the description is largely sufficient for simple usage.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, and the parameter description is clear. The tool description adds no additional semantic information beyond what is already in the schema, so a baseline score of 3 is appropriate.

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 specifies a clear verb ('lookup') and resource ('price/stock for up to 20 products'), with explicit identifiers (id, SKU, or name). It distinguishes from siblings like search_products and get_product by focusing on bulk lookup of specific items.

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 includes guidance 'Use when tracking specific items rather than browsing', providing clear context on when to use this tool. It indirectly contrasts with browsing tools, but does not explicitly mention alternatives or exclusions.

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

Deploy Server