Crawlora MCP

tiffany_search

Read-only

Search Tiffany & Co.'s product catalog by free-text keyword: normalized product summaries with USD pricing, live stock status, material, gemstone, collection, and designer. sort selects recommended (default), price_asc, price_desc, or newest. A genuine non-matching keyword returns a well-formed empty result.

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": {
      "keyword": "<keyword>"
    },
    "name": "tiffany_search"
  }
}

Input Schema

Name	Required	Description
`page`	No	One-based page
`sort`	No	Sort order. Documented values: recommended, price_asc, price_desc, newest.
`color`	No	Color filter -- see tiffany-filters
`gender`	No	Gender filter -- see tiffany-filters
`keyword`	Yes	Search keyword
`designer`	No	Designer/collection filter -- see tiffany-filters
`gemstone`	No	Gemstone filter -- see tiffany-filters
`material`	No	Material filter -- see tiffany-filters
`per_page`	No	Results per page
`product_type`	No	Product type filter -- see tiffany-filters

Output Schema

Name	Required	Description	Default
`data`	Yes	The tool result payload (shape varies per tool; see each tool's docs resource).

Schema Changelog

Changes observed during successful MCP inspections.

Changed10 schema fields changedOct 7, 2026
- addedInput schema / properties / color / description
```
Added value: +"Color filter -- see tiffany-filters"
```
- addedInput schema / properties / designer / description
```
Added value: +"Designer/collection filter -- see tiffany-filters"
```
- addedInput schema / properties / gemstone / description
```
Added value: +"Gemstone filter -- see tiffany-filters"
```
- addedInput schema / properties / gender / description
```
Added value: +"Gender filter -- see tiffany-filters"
```
- addedInput schema / properties / keyword / description
```
Added value: +"Search keyword"
```
- addedInput schema / properties / material / description
```
Added value: +"Material filter -- see tiffany-filters"
```
- addedInput schema / properties / page / description
```
Added value: +"One-based page"
```
- addedInput schema / properties / per_page / description
```
Added value: +"Results per page"
```
- addedInput schema / properties / product_type / description
```
Added value: +"Product type filter -- see tiffany-filters"
```
- addedInput schema / properties / sort / description
```
Added value: +"Sort order. Documented values: recommended, price_asc, price_desc, newest."
```
First observedOct 7, 2026

TDQS

A3.7/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true. The description adds real behavioral detail beyond that: results are normalized summaries with USD pricing and live stock status, and a non-matching keyword returns a well-formed empty result rather than an error. That empty-result guarantee is exactly the kind of context annotations cannot carry.

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 tight sentences, front-loaded with the action and return content, then sort behavior, then edge-case behavior. Little waste, though the returned-facets enumeration slightly overlaps the output schema.

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?

With a full output schema, 100% param coverage, and read-only annotations, the description only needs to frame purpose and edge cases, which it does. The one gap is that it never routes the agent away from near-identical Tiffany search siblings.

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 all ten parameters. The description restates the sort values and adds the 'recommended' default, but the schema already lists documented sort values, so the added meaning is marginal and the 3 baseline is appropriate.

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?

States a specific verb ('Search') and resource ('Tiffany & Co.'s product catalog') and enumerates the returned facets, so an agent knows what it gets. It does not, however, distinguish itself from close siblings like tiffany_content_search, tiffany_category, or tiffany_product.

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?

Gives the default sort value and the non-match behavior, which is implicitly useful usage context. But it never says when to prefer this over tiffany_content_search or when to grab filters from tiffany_filters first, so routing is left to inference.

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

All Crawlora MCP tools Inspect

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.