rijksmuseum-mcp+

Overview Schema Source Related Servers Discussions Admin

Get Artwork Image

get_artwork_image

Open an interactive deep-zoom viewer for any Rijksmuseum artwork by providing its object number. Returns metadata and a viewer link to explore the piece in detail.

Instructions

Opens an interactive deep-zoom viewer for the user. Use only when they ask to see, show, or view an artwork — not for list, summary, count, or text-only requests. Not for visual analysis by the LLM — use inspect_artwork_image to get image bytes. Not all artworks have images available. Returns metadata and a viewer link, not the image bytes themselves; do not construct or fetch IIIF image URLs manually (downloadable images are on rijksmuseum.nl).

Input Schema

TableJSON Schema

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

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

Behavior5/5

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

The description discloses important behavior beyond the annotations: it returns metadata and a viewer link rather than image bytes, not all artworks have images, and agents should not manually construct or fetch IIIF URLs. It also implies a stateful viewer interaction, consistent with openWorldHint. No contradiction with the annotations.

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 compact yet information-dense: each sentence serves a purpose, starting with the core action and then layering usage constraints, alternatives, caveats, and return-type expectations. It avoids redundancy with the schema.

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 tool that opens an interactive viewer, the description covers what it returns, when it should be used, who the alternative is for, edge cases (missing images), and an explicit warning about URL construction. The presence of an output schema further reduces the need to explain return values.

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?

There is only one parameter, objectNumber, and the input schema already describes it with an example, giving 100% schema coverage. The description adds context around image availability but does not need to add parameter-specific semantics. 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?

The description clearly states what the tool does ('Opens an interactive deep-zoom viewer for the user') and distinguishes it from inspect_artwork_image, which returns image bytes. It also scopes the resource to artwork viewing, making the purpose unmistakable.

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?

The description gives explicit use conditions ('Use only when they ask to see, show, or view an artwork'), explicit exclusions ('not for list, summary, count, or text-only requests'), and names a concrete alternative ('use inspect_artwork_image to get image bytes'). This is strong routing guidance.

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

Deploy Server