Crawlora MCP

Official

Overview Schema Source Related Servers Discussions Admin

petsmart_suggest

Returns PetSmart search suggestions for partial text with relative popularity and exact product match counts; use before searching, optionally for the Canadian catalog.

Instructions

Get PetSmart search suggestions. Returns PetSmart's own search suggestions for partial text, each with its relative popularity and how many products it matches exactly. Useful for completing a search phrase before calling /petsmart/search. Pass country=ca for the Canadian catalog.

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": {
      "query": "<query>"
    },
    "name": "petsmart_suggest"
  }
}

Input Schema

Name	Required	Description
`limit`	No	Optional suggestions returned. Defaults to 8, maximum 20.
`query`	Yes	Partial search text to complete, for example dog fo.
`country`	No	Optional catalog: us (default) or ca for the Canadian store, which has its own products (about 9,000), categories, filters and prices.

Schema Changelog

Changes observed during successful MCP inspections.

Addedv1.17.20Nov 12, 2026

TDQS

A3.6/5.0

Behavior3/5

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

With no annotations, the description carries the full disclosure burden. It does useful work by describing the return shape (popularity plus exact-match count) and the country=catalog behavior including the Canadian store's separate ~9,000-product catalog. It says nothing about rate limits, failure modes for partial text, or empty-result behavior, which a no-annotation definition ideally would.

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?

Three compact sentences, front-loaded with the purpose, then the return characteristics, then the usage pointer and country note. No filler; the only minor redundancy is the country sentence restating what the schema enum already says.

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?

There is no output schema, so describing what comes back (suggestions with popularity and match counts) plus the catalog scope covers the essentials for a low-complexity, three-parameter read tool. Remaining gaps are edge cases (no matches, malformed partial text) rather than core calling information.

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%, so the schema already documents limit, query, and the us/ca enum with catalog details. The description's "Pass country=ca for the Canadian catalog" largely repeats the enum description rather than adding new meaning, so the baseline of 3 applies.

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 gives a specific verb and resource ("Get PetSmart search suggestions") and characterizes the payload (suggestions with relative popularity and exact-match counts), which separates it from product-listing tools. The reference to "/petsmart/search" is stated as an endpoint path rather than the sibling tool name `petsmart_search`, so the differentiation is clear in meaning but not perfectly matched to the tool namespace.

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 states a concrete use case: completing a search phrase before calling the search tool, which effectively names the downstream alternative. It stops short of explicit exclusions (e.g., that this returns no products or prices and shouldn't be used to retrieve results).

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

Deploy Server