Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

tiffany_search

Search Tiffany & Co.'s product catalog by keyword and filters, returning product summaries with USD prices, stock status, material, gemstone, collection, and designer.

Instructions

Search Tiffany & Co. products. Searches Tiffany & Co.'s product catalog by free-text keyword. Returns product summaries with USD pricing, live stock status, material, gemstone, collection, and designer. sort selects recommended (default), price_asc, price_desc, or newest. material, gemstone, color, product_type, gender, and designer are optional single-value filters -- see tiffany-filters for the live covered value space for each. A genuine non-matching keyword, or a filter combination with no matches, returns a well-formed empty result (zero total_products).

Input Schema

NameRequiredDescriptionDefault
pageNoOne-based page
sortNoSort order
colorNoColor filter -- see tiffany-filters
genderNoGender filter -- see tiffany-filters
keywordYesSearch keyword
designerNoDesigner/collection filter -- see tiffany-filters
gemstoneNoGemstone filter -- see tiffany-filters
materialNoMaterial filter -- see tiffany-filters
per_pageNoResults per page
product_typeNoProduct type filter -- see tiffany-filters

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.5

TDQS

A3.8/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 burden. It does disclose return content (USD pricing, live stock status, material, gemstone, collection, designer) and the well-formed empty-result behavior, which is genuinely useful. However it omits pagination behavior despite page/per_page parameters and says nothing about auth or rate limits.

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?

Purpose is front-loaded, followed by return content, sort, filters, and edge-case behavior in a logical order. Every sentence earns its place, though the second sentence slightly restates the first.

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 10-parameter search tool with no annotations and no output schema, the description covers purpose, returns, sort/filter usage, and empty-result handling adequately. The main gap is pagination behavior and total-count semantics.

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

Parameters4/5

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

Schema coverage is 100%, so baseline is 3, but the description adds real meaning: it names the default sort ('recommended'), enumerates the filter dimensions, notes they are single-value, and routes the agent to tiffany-filters for allowed values. It does not explain page/per_page semantics.

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 opens with a specific verb+resource ('Search Tiffany & Co. products') and clarifies the mechanism ('by free-text keyword' against the product catalog). This clearly separates it from category/product-detail siblings, though it never names an alternative explicitly, so it stops short of a 5.

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 gives clear context for how the tool is used: free-text keyword plus optional single-value filters, with an explicit pointer to tiffany-filters for the live covered value space. It does not state when to prefer this over siblings like tiffany_category or tiffany_product, so no exclusions are offered.

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