Skip to main content
Glama
Sign In

Crawlora MCP

by net.crawlora
OverviewDiscussionsAdmin

petsmart_search

Read-only

Search PetSmart's catalog of about 20,000 products and return one page of results with SKU id, name, brand, price, images, rating and availability flags. Narrow by keyword, category path, brand, price range, minimum rating or any catalog filter, and order by relevance, price, best sellers, top rated or new arrivals. Get valid category and filter values from petsmart_categories and petsmart_search_filters; results page to a maximum of 10,000. Pass country=ca for the Canadian catalog.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "petsmart_search"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNoOptional 1-based page number. Defaults to 1.
sortNoOptional ordering: relevance (default), price_asc, price_desc, best_sellers, top_rated or new_arrivals.
brandNoOptional exact brand name. Find values with /petsmart/search/filters using facet=brand and facet_query.
limitNoOptional products per page. Defaults to 24, maximum 100.
queryNoOptional keyword. Omit to browse the whole catalog or a category.
filterNoOptional catalog filters as name:value, repeatable. Names and values come from /petsmart/search/filters. Different names combine with AND; repeating one name combines its values with OR.
countryNoOptional catalog: us (default) or ca for the Canadian store. Categories, filters, products and prices differ by country.
categoryNoOptional category path, from /petsmart/categories' path field. Includes the category's descendants.
max_priceNoOptional maximum price in dollars.
min_priceNoOptional minimum price in dollars.
min_ratingNoOptional minimum average customer rating, 0 to 5.

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.1/5.0
Behavior4/5

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

Annotations already cover read-only and open-world, but the description adds non-obvious behavior: results are a single page, deep paging is capped at 10,000 results, and the Canadian catalog has separate categories, filters and prices. It does not describe rate limits or filter-validation failure modes, keeping it short of a 5.

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?

Front-loaded with purpose and return fields, then filtering/sorting, then prerequisites, then the paging cap and country switch. Dense but every clause carries information; two long sentences could be split for scanability.

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 an 11-parameter search with an output schema, the description covers scope, filtering, sorting, prerequisite lookups, paging limits and the country variant. The output schema and high-coverage parameter schema remove the need to explain return shape or individual parameter syntax.

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 parameters already document defaults, enum-like sort values, the name:value filter syntax with AND/OR behavior, and the country differences. The only genuinely new detail is the 10,000-result pagination ceiling, so the description sits at the baseline rather than compensating for gaps.

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?

Opens with a specific verb and resource ("Search PetSmart's catalog") plus scope (about 20,000 products) and enumerates the returned fields (SKU, name, brand, price, images, rating, availability). An agent can distinguish it from petsmart_product, petsmart_categories and petsmart_suggest without opening a schema.

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?

Explicitly routes the agent to petsmart_categories and petsmart_search_filters before calling, and states the country=ca switch condition. It does not mention when to prefer petsmart_product for a single SKU or petsmart_suggest for autocomplete, so routing is good but not exhaustive.

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