mcp-livedatapro

checkProductInventory

Real-time stock levels, exact warehouse quantities available, and backorder status for e-commerce stores. Use when verifying real-time physical warehouse stock quantities, variant availability, fulfillment method (FBA vs Merchant), and restock dates for an e-commerce product URL or SKU. Do not use for historical price comparison (use getEcommercePricing) or return policies (use getMerchantReturnPolicy).

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": {
      "product_url_or_sku": "<product_url_or_sku>"
    },
    "name": "checkProductInventory"
  }
}

Input Schema

Name	Required	Description	Default
`product_url_or_sku`	Yes	Full e-commerce product page URL (Shopify, WooCommerce, Amazon) or merchant SKU.

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedOct 24, 2026
- addedInput schema / additionalProperties
```
Added value: +false
```
- addedInput schema / properties / product_url_or_sku / examples
```
Added value: +[
+  "https://store.example.com/products/pro-keyboard"
+]
```
- addedInput schema / properties / product_url_or_sku / minLength
```
Added value: +3
```

Changed1 schema field changedOct 24, 2026

changedInput schema / properties / product_url_or_sku / description

Previous value: -"Target product URL (Shopify, WooCommerce, Amazon) or SKU"New value: +"Full e-commerce product page URL (Shopify, WooCommerce, Amazon) or merchant SKU."

First observedOct 21, 2026

TDQS

A4.1/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 usefully discloses that the data is real-time and covers physical warehouse stock, backorders, fulfillment method, and restock dates, but it does not mention permissions, rate limits, source coverage, missing-SKU behavior, or explicitly confirm that the operation is read-only.

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?

The description is front-loaded with the core data returned, followed by usage guidance and exclusions. It is efficient overall, with only mild duplication between the first sentence and the 'Use when' clause.

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 one-parameter lookup with no output schema and no annotations, the description gives enough information to invoke it correctly and explains the categories of data returned. It could be stronger by noting response shape, error behavior, or platform coverage, but the core context is present.

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 single parameter is already documented as a full product URL or merchant SKU with an example. The description reinforces the accepted input types but adds no format, validation, or interpretation details beyond the schema.

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 states a specific resource and data set: real-time stock levels, exact warehouse quantities, backorder status, variant availability, fulfillment method, and restock dates. It clearly distinguishes this tool from getEcommercePricing and getMerchantReturnPolicy, so an agent can identify its role without opening schemas.

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

Usage Guidelines5/5

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

It explicitly says when to use the tool for physical warehouse stock quantities, variant availability, FBA vs Merchant fulfillment, and restock dates. It also names two concrete alternatives and the cases where those alternatives should be used instead.

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

All mcp-livedatapro tools Inspect

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

Need Help?