rijksmuseum-mcp+

Overview Schema Source Related Servers Discussions Admin

Get Conservation History

get_conservation_history

Read-onlyIdempotent

Get technical examination and restoration records for one artwork by object number—X-ray, dendrochronology, paint samples, infrared, conservation treatments, and provenance excerpt—when detailed history is needed.

Instructions

Technical examinations and restoration history for ONE artwork. Follows get_artwork_details / a search result, by objectNumber. Returns technical examinations (X-ray, dendrochronology, paint samples, infrared), conservation/restoration treatment events, a count of recorded signature/inscription marks (use search_inscriptions for the actual transcriptions), and a short provenance excerpt. Not for general metadata — use get_artwork_details. Not for transcribed inscriptions — use search_inscriptions. Not for aggregate counts — use collection_stats.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`objectNumber`	Yes	The object number of the artwork (e.g. 'SK-C-5', 'SK-A-4878').

Output Schema

TableJSON Schema

Name	Required	Description
`error`	No
`title`	Yes
`creator`	Yes
`warnings`	No
`examinations`	Yes	Technical examinations / forensic reports (X-ray, dendrochronology, paint samples, infrared, …). Most-recent first.
`objectNumber`	Yes
`attributionMarks`	Yes	Presence of signature/inscription marks only — a count, not content. The harvested rows carry no transcribed text and their carrier URIs do not resolve; use get_artwork_details.parsedInscriptions / search_inscriptions for the actual transcriptions.
`conservationHistory`	Yes	Restoration / conservation treatment events. Most-recent first.
`provenanceTextSummary`	Yes	Short excerpt of the raw provenance text, for forensic cross-reference. Null when absent.
`examinationsTotalCount`	Yes
`conservationHistoryTotalCount`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed26 schema fields changedv0.90.1Sep 6, 2026
- removedOutput schema / properties / conservationHistory / items / properties / date / anyOf
```
Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
```
- addedOutput schema / properties / conservationHistory / items / properties / date / type
```
Added value: +[
+  "string",
+  "null"
+]
```
- removedOutput schema / properties / conservationHistory / items / properties / dateBegin / anyOf
```
Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
```
- addedOutput schema / properties / conservationHistory / items / properties / dateBegin / type
```
Added value: +[
+  "string",
+  "null"
+]
```
- removedOutput schema / properties / conservationHistory / items / properties / dateEnd / anyOf
```
Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
```
- addedOutput schema / properties / conservationHistory / items / properties / dateEnd / type
```
Added value: +[
+  "string",
+  "null"
+]
```
- removedOutput schema / properties / conservationHistory / items / properties / description / anyOf
```
Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
```
- addedOutput schema / properties / conservationHistory / items / properties / description / type
```
Added value: +[
+  "string",
+  "null"
+]
```
- removedOutput schema / properties / conservationHistory / items / properties / modifierUri / anyOf
```
Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
```
- addedOutput schema / properties / conservationHistory / items / properties / modifierUri / type
```
Added value: +[
+  "string",
+  "null"
+]
```
- removedOutput schema / properties / creator / anyOf
```
Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
```
- addedOutput schema / properties / creator / type
```
Added value: +[
+  "string",
+  "null"
+]
```
- removedOutput schema / properties / examinations / items / properties / date / anyOf
```
Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
```
- addedOutput schema / properties / examinations / items / properties / date / type
```
Added value: +[
+  "string",
+  "null"
+]
```
- removedOutput schema / properties / examinations / items / properties / dateBegin / anyOf
```
Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
```
- addedOutput schema / properties / examinations / items / properties / dateBegin / type
```
Added value: +[
+  "string",
+  "null"
+]
```
- removedOutput schema / properties / examinations / items / properties / dateEnd / anyOf
```
Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
```
- addedOutput schema / properties / examinations / items / properties / dateEnd / type
```
Added value: +[
+  "string",
+  "null"
+]
```
- removedOutput schema / properties / examinations / items / properties / examiner / anyOf
```
Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
```
- addedOutput schema / properties / examinations / items / properties / examiner / type
```
Added value: +[
+  "string",
+  "null"
+]
```
- removedOutput schema / properties / examinations / items / properties / reportTypeLabel / anyOf
```
Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
```
- addedOutput schema / properties / examinations / items / properties / reportTypeLabel / type
```
Added value: +[
+  "string",
+  "null"
+]
```
- removedOutput schema / properties / provenanceTextSummary / anyOf
```
Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
```
- addedOutput schema / properties / provenanceTextSummary / type
```
Added value: +[
+  "string",
+  "null"
+]
```
- removedOutput schema / properties / title / anyOf
```
Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
```
- addedOutput schema / properties / title / type
```
Added value: +[
+  "string",
+  "null"
+]
```
First observedv0.90.0Jul 4, 2026

TDQS

A4.7/5.0

Behavior5/5

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

Annotations already mark this as read-only, idempotent, and non-destructive. The description goes further by disclosing the concrete contents: technical examinations, treatment events, a count of signature/inscription marks (not transcriptions), and a provenance excerpt. This fully sets agent expectations.

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?

Four dense sentences, each earning its place: scope, sequencing, return contents, and explicit exclusions. No filler or repetition of annotation information.

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 single-parameter, read-only tool with an output schema, the description fully covers when to use it, how to use it, what it returns, and what it explicitly avoids. Nothing critical is missing.

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 coverage is 100% and the only parameter, objectNumber, already has a clear description with examples. The description's 'by objectNumber' adds little beyond the schema, so the 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?

States a specific verb+resource ('Technical examinations and restoration history for ONE artwork') and enumerates exactly what it returns. Explicitly distinguishes itself from get_artwork_details and other tools by declaring what it is not for.

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

Usage Guidelines5/5

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

Provides explicit sequencing guidance: use after get_artwork_details or a search result, keyed by objectNumber. Also gives clear exclusion criteria with named alternatives for general metadata, transcriptions, and aggregate counts.

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

Deploy Server