Skip to main content
Glama
samiashi

chrono24-mcp

by samiashi
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Get watch details

get_watch
Read-only

Retrieve complete Chrono24 listing details by ID: reference, specs, box/papers, dealer info, photos, and canonical URL.

Instructions

Get full details for one Chrono24 listing by id: reference, specs (movement, case, caliber), box/papers, dealer info, all photos and the canonical URL.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesChrono24 listing id (digits from a listing URL --id<id>.htm)

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
idNo
yearYes
brandYes
modelYes
scopeYes
specsYes
genderYes
imagesYes
currencyYes
locationYes
movementYes
conditionYes
referenceYes
sellerIdsNocustomerId powers get_dealer_listings; dealerId powers get_dealer_ratings
priceValueYes
descriptionYes
shipsWithinNoShipping estimate, e.g. '1 - 3 days'
availabilityYese.g. 'Item is in stock' - empty when the page does not say
canonicalUrlNo
caseDiameterYes
caseMaterialYes
priceDisplayYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.6.0
    • removedInput schema / additionalProperties
      Removed value: -false
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": false,
+  "properties": {
+    "availability": {
+      "description": "e.g. 'Item is in stock' - empty when the page does not say",
+      "type": "string"
+    },
+    "brand": {
+      "type": "string"
+    },
+    "canonicalUrl": {
+      "type": "string"
+    },
+    "caseDiameter": {
+      "type": "string"
+    },
+    "caseMaterial": {
+      "type": "string"
+    },
+    "condition": {
+      "type": "string"
+    },
+    "currency": {
+      "type": "string"
+    },
+    "description": {
+      "type": "string"
+    },
+    "gender": {
+      "type": "string"
+    },
+    "id": {
+      "type": "string"
+    },
+    "images": {
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "location": {
+      "type": "string"
+    },
+    "model": {
+      "type": "string"
+    },
+    "movement": {
+      "type": "string"
+    },
+    "priceDisplay": {
+      "type": "string"
+    },
+    "priceValue": {
+      "type": [
+        "number",
+        "null"
+      ]
+    },
+    "reference": {
+      "type": "string"
+    },
+    "scope": {
+      "type": "string"
+    },
+    "sellerIds": {
+      "additionalProperties": false,
+      "description": "customerId powers get_dealer_listings; dealerId powers get_dealer_ratings",
+      "properties": {
+        "customerId": {
+          "type": [
+            "string",
+            "null"
+          ]
+        },
+        "dealerId": {
+          "type": [
+            "string",
+            "null"
+          ]
+        }
+      },
+      "required": [
+        "customerId",
+        "dealerId"
+      ],
+      "type": "object"
+    },
+    "shipsWithin": {
+      "description": "Shipping estimate, e.g. '1 - 3 days'",
+      "type": "string"
+    },
+    "specs": {
+      "additionalProperties": {
+        "type": "string"
+      },
+      "propertyNames": {
+        "type": "string"
+      },
+      "type": "object"
+    },
+    "year": {
+      "type": "string"
+    }
+  },
+  "required": [
+    "brand",
+    "model",
+    "reference",
+    "priceDisplay",
+    "priceValue",
+    "currency",
+    "condition",
+    "year",
+    "movement",
+    "caseMaterial",
+    "caseDiameter",
+    "gender",
+    "scope",
+    "availability",
+    "description",
+    "location",
+    "images",
+    "specs"
+  ],
+  "type": "object"
+}
  2. First observedv0.4.0

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, so the safety profile is covered. The description adds value by listing the response contents: reference, specs, box/papers, dealer info, photos, and canonical URL. It does not go into rate limits or external data freshness, but the read-only annotation lowers the burden.

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?

The description is a single dense sentence. It leads with the action and resource, then packs the most relevant return categories into a compact colon-separated list with no filler or redundancy.

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-id read tool with an output schema, readOnlyHint=true, and a fully described parameter, the description is sufficient. An agent can call it safely and know what to expect without missing prerequisites or important caveats.

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?

The input schema documents the single 'id' parameter thoroughly, including a pattern and an example of extracting it from a listing URL. The description only repeats 'by id' and adds no extra parameter semantics beyond what the schema already provides.

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 opens with a specific verb and resource: 'Get full details for one Chrono24 listing by id'. It then enumerates the concrete content returned, which clearly differentiates this from siblings like search_listings, get_watches, and get_watch_photos.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

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

The phrase 'one ... listing by id' implies the tool is for retrieving a single listing when the id is already known, but it never explicitly says when to prefer this over search_listings or get_watches, nor does it mention a way to obtain an id. Usage context is implied rather than stated.

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

Deploy Server

Other Tools