Crawlora MCP

tiffany_suggest

Read-only

Tiffany & Co.'s own search-box suggestions (typeahead) for a partial query: suggested search phrases, each with its own live total result count on the product catalog. Not product data.

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": "tiffany_suggest"
  }
}

Input Schema

Name	Required	Description	Default
`query`	Yes	Partial search query

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.

Changed1 schema field changedOct 7, 2026
- addedInput schema / properties / query / description
```
Added value: +"Partial search query"
```
First observedOct 5, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, so the safety profile is covered. The description adds useful behavioral context: results are suggested phrases, each carrying a live total result count over the product catalog, which tells the agent what the payload carries beyond a plain string list.

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?

One tight sentence front-loads what it is, and the short 'Not product data' clause earns its place by preempting a plausible mistake. Nothing wasted.

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?

An output schema exists, so return values need no prose explanation, and the description covers what/how/scope adequately for a single-parameter lookup. Complete enough to invoke correctly without further reading.

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 coverage is 100% and there is only one parameter ('query', 'Partial search query'). The description's phrase 'partial query' mirrors the schema exactly, adding no syntax or format detail beyond it. Baseline 3 for a fully documented single 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?

States a specific resource (Tiffany & Co.'s search-box suggestions / typeahead) and verb (suggest for a partial query), and explicitly disambiguates from siblings with 'Not product data,' distinguishing it from tiffany_search and 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 Guidelines4/5

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

The typeahead framing plus 'Not product data' implicitly tells the agent this is for autocomplete-style phrase discovery rather than catalog retrieval, and the partial-query input signals the usage context. However, it never names an explicit alternative or when-not-to-use condition.

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.

Resources

Need Help?