Skip to main content
Glama
kintopp

rijksmuseum-mcp+

by kintopp
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Get Conservation History

get_conservation_history
Read-onlyIdempotent

Retrieve technical examinations and conservation/restoration history for a single artwork using its object number.

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
NameRequiredDescriptionDefault
objectNumberYesThe object number of the artwork (e.g. 'SK-C-5', 'SK-A-4878').

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
errorNo
titleYes
creatorYes
warningsNo
examinationsYesTechnical examinations / forensic reports (X-ray, dendrochronology, paint samples, infrared, …). Most-recent first.
objectNumberYes
attributionMarksYesPresence 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.
conservationHistoryYesRestoration / conservation treatment events. Most-recent first.
provenanceTextSummaryYesShort excerpt of the raw provenance text, for forensic cross-reference. Null when absent.
examinationsTotalCountYes
conservationHistoryTotalCountYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.90.2
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
    • changedOutput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
  2. Changed26 schema fields changedv0.90.1
    • 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"
+]
  3. First observedv0.90.0

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and non-destructive behavior, so the safety profile is covered. The description adds genuine behavioral context beyond that: the concrete examination types returned, the treatment-event list, the signature count, and the crucial nuance that the mark count is a count only while transcriptions live in search_inscriptions.

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?

Front-loads the one-line purpose, then the invocation context, then the return contents, then the three routing exclusions. Every sentence carries distinct information; nothing is padding.

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?

An output schema exists, so return values need not be explained, yet the description still summarizes the payload and wires the agent to the right sibling for each adjacent need. Nothing required to call this correctly 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 description coverage is 100% and the single parameter is fully documented with format examples in the schema itself. The description only restates 'by objectNumber', adding no syntax or constraint information beyond the structured fields, so the baseline 3 applies.

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 and resource ('technical examinations and restoration history'), scopes it to exactly ONE artwork identified by objectNumber, and enumerates the returned content types. An agent can distinguish it from get_artwork_details and search_inscriptions without opening any schema.

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?

Gives explicit when-to-use context ('Follows get_artwork_details / a search result, by objectNumber') plus three explicit exclusions naming the correct alternative for each ('Not for general metadata — use get_artwork_details', 'Not for transcribed inscriptions — use search_inscriptions', 'Not for aggregate counts — use collection_stats').

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