chrono24-mcp

Overview Schema Source Related Servers Discussions Admin

Find brand models

find_models

Read-only

Retrieve a brand's model catalog with model names, slugs, and numeric IDs to pair with search filters for precise watch listings.

Instructions

List a brand's model catalog (model name, slug and numeric model id). Pair the model id with search_listings' models param and the brand id with manufacturerIds for precise searches.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`brand`	Yes	Brand name (e.g. 'Rolex'), brand id from list_brands (e.g. '221'), or slug

Output Schema

TableJSON Schema

Name	Required	Description	Default
`note`	No
`slug`	No
`brand`	No
`count`	Yes
`models`	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": {
+    "brand": {
+      "additionalProperties": false,
+      "properties": {
+        "id": {
+          "type": "string"
+        },
+        "name": {
+          "type": "string"
+        },
+        "slug": {
+          "type": "string"
+        }
+      },
+      "required": [
+        "id",
+        "name"
+      ],
+      "type": "object"
+    },
+    "count": {
+      "type": "number"
+    },
+    "models": {
+      "items": {
+        "additionalProperties": false,
+        "properties": {
+          "modelId": {
+            "type": "string"
+          },
+          "name": {
+            "type": "string"
+          },
+          "slug": {
+            "type": "string"
+          }
+        },
+        "required": [
+          "modelId",
+          "slug",
+          "name"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "note": {
+      "type": "string"
+    },
+    "slug": {
+      "type": "string"
+    }
+  },
+  "required": [
+    "count",
+    "models"
+  ],
+  "type": "object"
+}

First observedv0.4.0Aug 26, 2026

TDQS

A4.1/5.0

Behavior3/5

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

Annotations already convey readOnlyHint and openWorldHint, so the safety profile is covered. The description adds value by revealing exact output fields and the numeric nature of the model id, but it does not go into deeper behavior such as pagination, ordering, or completeness guarantees. This is acceptable given the simple read-only nature and existing annotations.

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, no filler. The first sentence states what the tool returns; the second sentence gives actionable downstream guidance. Everything present earns its place.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a one-parameter read-only tool with a detailed schema and output schema, the description is fully sufficient. It covers the purpose, the returned fields, and how to use the model id and brand id in related searches.

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% and already explains the brand parameter with examples and accepted input forms (name, id, or slug). The description reinforces the connection to list_brads and search_listings, but does not add significant new parameter meaning beyond the schema.

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 clearly states the verb ('List') and the resource ('a brand's model catalog'), and lists the output fields (model name, slug, numeric id). It is easy to distinguish from the sibling tool list_brands, which returns brands rather than 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 explicitly tells the agent how to use the results downstream by pairing the model id with search_listings' models param and the brand id with manufacturerIds. It gives clear context for when this tool is useful, though it does not explicitly state when not to use it or name alternatives beyond the integration hint.

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