Crawlora MCP

tiffany_category

Read-only

One page of a Tiffany & Co. category/browse listing. category is a category id from tiffany_categories's own id field. sort selects recommended (default), price_asc, price_desc, or newest. A hub-level or emptied-out category id returns a well-formed empty result rather than an error.

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": {
      "category": "<category>"
    },
    "name": "tiffany_category"
  }
}

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
`category`	Yes	Category id -- see tiffany-categories
`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 / category / description
```
Added value: +"Category id -- see tiffany-categories"
```
- 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 / 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.9/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, so the safety profile is covered. The description adds genuinely non-obvious behavior: pagination ('one page') and that hub-level or emptied-out category ids return a well-formed empty result instead of an error, which prevents an agent from misreading an empty page as failure.

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 sentences, front-loaded with what the tool returns, then id sourcing, sort options, and failure behavior. No filler, though it is fairly dense and could be slightly tighter.

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 an output schema present, return values need not be explained, and the empty-result and pagination behavior are disclosed. Filter semantics are delegated to tiffany-filters, which is acceptable for a browse tool but leaves the agent to consult another tool for the nine optional filters.

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 baseline is 3. The description adds limited value beyond the schema: it clarifies that category is an id field of tiffany_categories and documents the 'recommended' default for sort, but the filter params are left entirely to the tiffany-filters cross-reference.

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 resource and scope: 'One page of a Tiffany & Co. category/browse listing.' An agent can tell this is a browse/category-listing retrieval rather than a keyword search, which differentiates it from tiffany_search, though no sibling is named by contrast.

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 tells the agent where the required id comes from ('a category id from tiffany_categories's own id field') and enumerates valid sort modes with the default, which is clear operational context. It stops short of stating when to prefer tiffany_search or tiffany_filters over this tool.

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.