Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

chewy_suggest

Retrieve Chewy typeahead suggestions for partial search terms, yielding product, category, brand, and article recommendations. Omit the term to get popular searches and articles.

Instructions

Chewy search-box typeahead suggestions. Returns Chewy's own search-box typeahead result for a partial query term: search-term suggestions (some resolving directly to a category/brand browse URL via their own url field) plus a handful of educational-content article suggestions. term is a partial query, e.g. "salmon dog" or "blue buff". Omit term entirely to get what Chewy shows on an empty search box instead: its current Popular Searches (each resolving to a category or brand listing) and Popular Articles.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
termNoPartial search text, e.g. \

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv1.16.2
    • changedInput schema / properties / term / description
      Previous value: -"Partial search text"New value: +"Partial search text, e.g. \\"
    • changedInput schema / required
      Previous value: -[
-  "term"
-]New value: +[]
  2. Addedv1.16.0

TDQS

A4.6/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 behavioral disclosure burden. It does so well by explaining what is returned, that some suggestions resolve via a url field to category/brand pages, and what happens when term is omitted. It does not mention auth or rate limits, but those are low-risk concerns for a suggest endpoint.

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?

The description is longer than one sentence but every clause earns its place: core purpose first, then result composition, then examples, then empty-query behavior. Nothing is redundant or missing.

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?

For a one-optional-parameter tool with no annotations and no output schema, the description is complete: it covers input semantics, output types, URL behavior, and the no-term edge case. An agent has enough information to invoke it correctly and interpret the result.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The schema only describes term as partial search text, while the description adds concrete examples ('salmon dog', 'blue buff') and explains the critical optional-term behavior. This goes well beyond the schema and fully clarifies the only parameter.

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 first sentence states the exact function: Chewy search-box typeahead suggestions. It then specifies partial-query behavior and the two result types (search-term suggestions and educational articles), making it easy to distinguish from chewy_search and chewy_products.

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?

The description clearly establishes when to call it — for a partial typeahead query — and when to omit the term for Popular Searches/Articles. It does not explicitly name alternative tools like chewy_search for full searches, but the partial-query wording provides enough contextual guidance.

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