Skip to main content
Glama
Sign In
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

ohpolly_search_suggest

Fetch product, collection, and query suggestions from Oh Polly's predictive search to support autocomplete or discovery.

Instructions

Get Oh Polly search suggestions. Returns products, collections, and query suggestions from Oh Polly's (https://www.ohpolly.com) predictive search. The storefront URL is fixed server-side.

Input Schema

NameRequiredDescriptionDefault
qYesSearch query
limitNoMaximum results per type, defaults to 10 and supports up to 20
typesNoComma-separated suggestion types. Allowed values: product, collection, query

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.16.0

TDQS

A3.7/5.0
Behavior3/5

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

No annotations are provided, so the description carries the burden. It discloses that the storefront URL is fixed server-side (useful, non-obvious context) and that results are predictive, but says nothing about rate limits, auth, caching, or pagination behavior.

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 short sentences, front-loaded with the core action, then the return shape, then a server-side note. No filler, though the parenthetical URL and the fixed-URL sentence are marginally redundant.

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 a three-parameter suggest tool with full schema coverage and no output schema, the description covers purpose, return categories, and the fixed-storefront constraint. What is missing is usage routing against the many sibling search/suggest tools.

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 the schema already documents q, limit, and types. The description's mention of 'products, collections, and query suggestions' loosely mirrors the types parameter but adds no syntax or format detail beyond the schema, so baseline 3 applies.

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 (Get) and resource (Oh Polly search suggestions) and enumerates exactly what comes back: products, collections, and query suggestions from a predictive search. This clearly distinguishes it from sibling tools like ohpolly_products or ohpolly_collections that return actual catalog entities.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is only implied by the word 'suggestions' – an agent can infer this is an autocomplete/typeahead endpoint. There is no explicit statement of when to prefer this over ohpolly_products or ohpolly_collections, and no exclusions or prerequisites given.

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