rijksmuseum-mcp+

Overview Schema Source Related Servers Discussions Admin

Remount Viewer

remount_viewer

Switch the artwork viewer to a different object while preserving the existing view UUID. Clears any user highlight because coordinates belong 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.

Changed2 schema fields changedv0.90.2Oct 2, 2026

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"

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.2/5.0

Behavior4/5

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

Annotations declare readOnlyHint=false but destructiveHint=false, and the description adds genuinely new behavioral context: an existing user highlight is cleared because its coordinates belong to the previous artwork, and the viewUUID is preserved across the switch. That side-effect disclosure goes beyond what the annotations convey; only the lack of failure/error behavior keeps it from a 5.

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 front-loaded sentences with zero filler: scope marker, invocation context, and the one non-obvious 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?

With an output schema present, return values need not be described, and the trigger plus the highlight-clearing effect cover the essential behavior. It is nearly complete for a narrow internal utility, missing only error/precondition behavior.

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 both parameters are documented there (viewUUID provenance from get_artwork_image, objectNumber meaning). The description reinforces the preserve-viewUUID contract but adds no new syntax or constraint, 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?

The description states a specific verb+resource ('switch the viewer to a different artwork') plus the key constraint ('while preserving the viewUUID'), which distinguishes it from the sibling navigate_viewer. The 'Internal:' prefix immediately frames its scope, so an agent can tell what it does without opening the schema.

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 gives a clear calling context: 'Called by the artwork-viewer iframe during in-viewer related navigation,' and 'Internal:' implies it is not meant for general agent use. It does not explicitly name an alternative (e.g. navigate_viewer) or state when not to call it, so it falls short of a 5.

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

Deploy Server