Skip to main content
Glama
Sign In

Crawlora MCP

by net.crawlora
OverviewDiscussionsAdmin

petsmart_product

Read-only

Return one PetSmart product's full public detail by SKU id from petsmart_search: price and sale range, full description as text and HTML, manufacturer and UPCs, category paths, size and flavor variation options, promotions, shipping dimensions and every catalog attribute under attributes. Pass country=ca for a Canadian SKU.

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"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesProduct SKU, from /petsmart/search's id field.
countryNoOptional catalog: us (default) or ca for the Canadian store. Categories, filters, products and prices differ by country.

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

A3.9/5.0
Behavior3/5

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

The readOnlyHint/openWorldHint annotations already establish that this is a safe, non-mutating public lookup, so the description's main job is added context. It contributes the 'full public detail' scope and the fact that description is returned in both text and HTML, but says nothing about failure behavior for a bad SKU or about per-country data divergence beyond the country flag.

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?

One front-loaded sentence plus a short country caveat, with no filler. The long comma-separated field enumeration is dense but every item is informative, though it reads as a wall of text rather than a structured list.

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 explain return values, and only two parameters exist with full schema coverage. What remains is minor: no note on missing/invalid SKUs or cross-country SKU mismatch, which is the main edge case for a country-switched detail 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 coverage is 100% and the schema already documents 'us (default) or ca' for country, so the description only restates it more tersely while adding the useful note that the id originates from petsmart_search's id field. That is marginal added meaning over the schema, hence baseline 3.

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?

States a specific verb and resource ('Return one PetSmart product's full public detail by SKU id') and enumerates exactly what the payload contains (price/sale range, description text and HTML, manufacturer/UPCs, category paths, variations, promotions, dimensions, attributes). It also anchors the id to petsmart_search, so an agent can separate it from the search and suggest siblings.

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 implies the correct workflow by saying the SKU comes 'from petsmart_search' and it gives a concrete branch for the Canadian catalog ('Pass country=ca for a Canadian SKU'). It stops short of naming alternatives such as petsmart_product_inventory for stock or stating what to do when a SKU is unknown.

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