Crawlora MCP

chrono24_facets

Read-only

Every value Chrono24 accepts for one of chrono24_search's advanced-search filter params, each with its own live listing count -- the discovery endpoint for condition, used_or_new, case_material, dial_color, bracelet_material, movement_type, gender, watch_type and stock_info. group takes the matching upstream group id: condition, usedOrNew, caseMaterial, dialColor, braceletMaterial, movementType, gender, watchType or stockInfo.

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": {
      "Group": "<Group>"
    },
    "name": "chrono24_facets"
  }
}

Input Schema

Name	Required	Description	Default
`Group`	Yes	Filter to list values for. Documented values: condition, usedOrNew, caseMaterial, dialColor, braceletMaterial, movementType, gender, watchType, stockInfo.

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 / Group / description

Added value: +"Filter to list values for. Documented values: condition, usedOrNew, caseMaterial, dialColor, braceletMaterial, movementType, gender, watchType, stockInfo."

First observedOct 5, 2026

TDQS

A4.3/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 a useful behavioral trait beyond annotations: each returned value carries its own live listing count, telling the agent the response is enriched with popularity/count data rather than a plain enum list.

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?

Two sentences, front-loaded with the core purpose and response characteristic, then the parameter mapping. The enumerations are long but each item is load-bearing given nine facets; minimal waste.

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?

Output schema exists, so return structure needn't be explained. For a single-param facet-discovery tool, the description covers purpose, response enrichment, and the param-to-group mapping. Only minor omission is any note on caching/freshness of the 'live' counts.

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% (baseline 3), but the description goes further by mapping human-readable filter names (used_or_new, case_material) to the actual upstream group ids the parameter takes (usedOrNew, caseMaterial), which is exactly the camelCase form the schema documents. This disambiguation adds real value beyond the schema text.

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?

The description states a specific verb+resource: the discovery endpoint returning all accepted values for each of chrono24_search's filter params, and it names the exact facet groups covered. An agent can distinguish it from chrono24_search and other chrono24_* siblings (brands, models, autocomplete) without opening the schema.

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 ties the tool to chrono24_search's advanced-search filter params, implicitly establishing when to call it (to discover valid filter values before searching). It does not state explicit exclusions or a step-by-step 'call this before search' instruction, so it stops short of 5.

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?