Skip to main content
Glama
Sign In

Crawlora MCP

by net.crawlora
OverviewDiscussionsAdmin

petsmart_product_inventory

Read-only

Return how many units of a PetSmart product each store reports, as store number and quantity with highest stock first, plus totals across every store with a record. Pass the SKU id from petsmart_search, and optionally store_id, min_quantity and limit. Store numbers are PetSmart's own and are not mapped to addresses.

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": {
      "id": "<id>"
    },
    "name": "petsmart_product_inventory"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesProduct SKU, from /petsmart/search's id field.
limitNoOptional stores returned, highest stock first. Defaults to 100, maximum 2000.
store_idNoOptional PetSmart store numbers to return, repeatable. Omit for every store with a record.
min_quantityNoOptional minimum units in stock for a store to be listed. Defaults to 0, which includes stores that are out of stock.

Output Schema

NameRequiredDescriptionDefault
dataYesThe tool result payload (shape varies per tool; see each tool's docs resource).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4/5.0
Behavior4/5

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

Annotations already establish this as a read-only, open-world call, so the description focuses on what the annotations cannot say: results are ordered highest-stock-first, totals are aggregated across all stores with a record, and coverage is limited to stores that actually report. The caveat that store numbers are not mapped to addresses is a genuinely useful usage constraint.

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?

Three short sentences with zero filler: the return payload and ordering come first, parameters second, and the store-number caveat last. Every sentence carries information an agent would otherwise have to infer.

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 an output schema present, the description need not spell out return structure, yet it still conveys aggregation, ordering and the address-mapping limitation. Only the freshness or geographic scope of the inventory data is unstated, which is a minor gap for a four-parameter read tool.

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 description coverage is 100 percent, so defaults, maximums and repeatability are already documented in the schema. The description restates store_id, min_quantity and limit at a high level and adds only the 'highest stock first' ordering nuance, which is the baseline expectation when the schema carries the detail.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific verb and resource ('Return how many units of a PetSmart product each store reports') and the shape of the answer (store number + quantity, totals). It implicitly routes away from petsmart_product by sourcing the id from petsmart_search, but never explicitly contrasts with the product-detail sibling.

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?

It explicitly says to pass the SKU id from petsmart_search and that store_id can be omitted to get every store with a record, which gives clear preconditions and defaults. It stops short of naming when an agent should use this versus petsmart_product, so no explicit exclusion is given.

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

All Crawlora MCP 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