Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

petsmart_product_inventory

Fetch a PetSmart product's per-store stock counts, highest stock first, with totals and filters for store numbers and minimum units. Unknown SKUs return a 404.

Instructions

Get one PetSmart product's stock count per store. Returns how many units of a product PetSmart reports in each store, as store number and quantity, highest stock first, with totals over every store that has a record (stores_with_record, stores_in_stock, total_units). Narrow with store_id (repeatable) and min_quantity; limit caps the list (default 100, maximum 2000) without changing the totals. Store numbers are PetSmart's own; PetSmart's store locator is not available anonymously, so this endpoint does not map them to addresses. An unknown SKU returns a 404.

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.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.20

TDQS

A4.2/5.0
Behavior4/5

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

No annotations are provided, so the description carries the full disclosure burden, and it does well here: it states the sort order (highest stock first), that limit truncates the list without changing the totals, that the totals cover every store with a record, and that an unknown SKU returns a 404. It also warns that store numbers cannot be resolved to addresses because the locator is not available anonymously. What is missing is any statement about auth or rate limits.

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?

It is three tight sentences, with the return shape front-loaded before the filtering knobs. Every clause carries information: ordering, totals semantics, limit behavior, the store-ID caveat, and the 404 case. Nothing is padding.

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 and no annotations, the description must describe the return shape, and it does: store number, quantity, and the three total fields. The 404 case and the store-ID caveat are also covered. It falls just short of complete because authentication, rate limits, and whether the call is read-only are left implicit.

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%, so the baseline is 3. The description still adds meaning the schema does not: limit 'caps the list ... without changing the totals', which is a non-obvious aggregation rule, and it reinforces that min_quantity defaults to 0, including out-of-stock stores.

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 leads with a specific verb and resource: 'Get one PetSmart product's stock count per store'. It then pins the scope further ('how many units of a product PetSmart reports in each store, as store number and quantity'), which is clearly distinct from a plain product-detail lookup or a catalog search.

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

Usage Guidelines3/5

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

Use is implied rather than stated. Narrowing behavior (store_id, min_quantity) and the limit default are explained, but the description never says when to pick this tool over an alternative, such as the product-detail tool or another retailer's inventory endpoint. It also gives no explicit exclusions.

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

Deploy Server

Other Tools