chrono24-mcp

Overview Schema Source Related Servers Discussions Admin

List watch brands

list_brands

Read-only

Retrieve Chrono24 watch brands and their numeric IDs, with optional substring filtering. Use a brand ID to search listings by manufacturer or a brand name to find models.

Instructions

List Chrono24 watch brands with their numeric ids (550+). Use an id with search_listings' manufacturerIds, or a name with find_models.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`query`	No	Optional case-insensitive substring filter on brand name, e.g. 'rolex' or 'lange'

Output Schema

TableJSON Schema

Name	Required	Description	Default
`count`	Yes
`brands`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedv0.6.0Sep 4, 2026

removedInput schema / additionalProperties
```
Removed value: -false
```

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": false,
+  "properties": {
+    "brands": {
+      "items": {
+        "additionalProperties": false,
+        "properties": {
+          "id": {
+            "type": "string"
+          },
+          "name": {
+            "type": "string"
+          }
+        },
+        "required": [
+          "id",
+          "name"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "count": {
+      "type": "number"
+    }
+  },
+  "required": [
+    "count",
+    "brands"
+  ],
+  "type": "object"
+}

First observedv0.4.0Aug 26, 2026

TDQS

A4/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true, so the read-only nature is covered. The description adds that there are 550+ brands and that ids are numeric, which is useful context, but it doesn't disclose details like default ordering or pagination.

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?

Two sentences with no waste: the first states the core purpose and output, the second gives integration guidance. Every sentence earns its place.

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?

The tool is simple (one optional parameter, read-only, output schema present). The description covers purpose, output shape, and relationship to siblings. It could mention that omitting query returns all brands, but that's inferable from the schema and the description's 'List ... brands' phrasing.

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% because the query parameter is fully documented as an optional case-insensitive substring filter. The description adds a note about using a name with find_models, but that's downstream usage rather than new parameter semantics. Baseline 3 is appropriate.

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 ('List') and resource ('Chrono24 watch brands') and specifies that it returns numeric ids. It also differentiates from siblings by showing how the ids/names are used with search_listings and find_models.

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 description provides concrete downstream usage: use an id with search_listings' manufacturerIds, or a name with find_models. It doesn't explicitly state when not to use this tool, but the context and sibling names make the selection clear.

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