rijksmuseum-mcp+

Overview Schema Source Related Servers Discussions Admin

Remount Viewer

remount_viewer

Load another artwork into the active viewer while preserving its viewUUID. Highlights are cleared because their coordinates refer to the previous artwork.

Instructions

Internal: switch the viewer to a different artwork while preserving the viewUUID. Called by the artwork-viewer iframe during in-viewer related navigation. Any user highlight is cleared on remount because its coordinates belong to the previous artwork.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`viewUUID`	Yes	Existing viewer UUID returned by a prior get_artwork_image call
`objectNumber`	Yes	Object number of the artwork to remount into the viewer

Output Schema

TableJSON Schema

Name	Required	Description
`url`	No
`date`	No
`error`	No
`title`	No
`width`	No
`height`	No
`creator`	No
`license`	No
`viewUUID`	No	Viewer session ID for use with navigate_viewer.
`iiifInfoUrl`	No
`objectNumber`	Yes
`physicalDimensions`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed8 schema fields changedv0.90.1Sep 6, 2026

removedOutput schema / properties / creator / anyOf

Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]

addedOutput schema / properties / creator / type
```
Added value: +[
+  "string",
+  "null"
+]
```

removedOutput schema / properties / date / anyOf

Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]

addedOutput schema / properties / date / type
```
Added value: +[
+  "string",
+  "null"
+]
```

removedOutput schema / properties / license / anyOf

Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]

addedOutput schema / properties / license / type
```
Added value: +[
+  "string",
+  "null"
+]
```

removedOutput schema / properties / physicalDimensions / anyOf

Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]

addedOutput schema / properties / physicalDimensions / type
```
Added value: +[
+  "string",
+  "null"
+]
```

First observedv0.90.0Jul 4, 2026

TDQS

A4.1/5.0

Behavior5/5

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

The description discloses a concrete side effect beyond the annotations: any user highlight is cleared on remount, and it explains why. It also states that the viewUUID is preserved. Given the annotations only provide false hints, this description carries the behavioral disclosure burden well.

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?

Three short sentences with no filler. The core action is front-loaded, followed by usage context and an important behavioral side effect. 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?

For a simple two-parameter tool with an output schema and explicit side-effect disclosure, the description is largely complete. The only minor gap is that it does not explicitly contrast itself with navigate_viewer, though the 'Internal' label and iframe call-site reduce ambiguity.

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%, so the baseline is 3. The description does not add additional meaning beyond the schema's own parameter descriptions for viewUUID and objectNumber.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description uses a specific verb ('switch') and resource ('viewer') and states the key invariant of preserving the viewUUID. The 'Internal' label and iframe call-site help separate it from more general tools, though it does not explicitly name or contrast with the sibling navigate_viewer.

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?

It clearly states when it is used: by the artwork-viewer iframe during in-viewer related navigation. The 'Internal' prefix signals this is not a general-purpose API. However, it does not explicitly say when not to use it or name alternatives like navigate_viewer.

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

Deploy Server