Skip to main content
Glama
Sign In

Crawlora MCP

by net.crawlora
OverviewDiscussionsAdmin

petsmart_suggest

Read-only

Return PetSmart's own search suggestions for partial text, each with its relative popularity and exact product match count. Use this to complete a phrase before calling petsmart_search. Requires query. 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

NameRequiredDescriptionDefault
limitNoOptional suggestions returned. Defaults to 8, maximum 20.
queryYesPartial search text to complete, for example dog fo.
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

A4.2/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnlyHint, openWorldHint), and the description adds genuinely new context: results are PetSmart's own suggestions with relative popularity and a product match count, and the country parameter changes the underlying catalog. It does not discuss latency, rate limits, or empty-suggestion behavior, keeping it just below the top mark.

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?

Four short sentences, front-loaded with the outcome, then sequencing, then the required parameter and the country variant. 'Requires query' mildly restates the schema's required list but is defensible as a call-order hint.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With annotations, an output schema, and full schema description coverage already present, the description supplies everything else an agent needs: what it returns, why to call it before search, and how country changes the catalog. Nothing material is missing.

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%, so all three parameters are already documented, which sets the baseline at 3. The description reinforces that query is required and highlights country=ca for the Canadian catalog, but adds no syntax, formatting, or limiting detail beyond what the schema supplies.

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 PetSmart's own search suggestions for partial text) and describes the payload (relative popularity plus exact product match count). It is clearly distinguishable from the sibling petsmart_search, which it explicitly names.

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?

Gives explicit sequencing guidance — use this to complete a phrase before calling petsmart_search — which routes the agent correctly. It stops short of saying when not to use it (e.g., a complete query that should go straight to petsmart_search), so it is strong but not fully 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