rijksmuseum-mcp+

Overview Schema Source Related Servers Discussions Admin

Get Artwork Image

get_artwork_image

Open an interactive deep-zoom viewer to see a Rijksmuseum artwork when the user asks to view or show it, returning metadata and a viewer link rather than image bytes.

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.

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

Behavior5/5

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

Annotations only declare readOnlyHint=false, openWorldHint=true, idempotentHint=false, destructiveHint=false; the description adds the substantive behavior behind that: it opens a viewer for the user, may fail because not all artworks have images, returns metadata plus a viewer link rather than bytes, and warns against hand-constructing IIIF URLs. This is exactly the beyond-annotations context that annotations cannot carry.

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 core action, then spends each following clause on a distinct failure mode (wrong request type, wrong tool, missing image, wrong expectation about return value). No filler and nothing repeated from the schema or annotations.

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 1-param tool with an output schema, all the failure modes an agent could hit are covered: usability exclusions, the sibling to use instead, image availability, and the exact nature of the return. Nothing needed to call it 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% with a single documented parameter ('The object number of the artwork (e.g. 'SK-C-5')'), so the schema already carries parameter meaning. The description adds no further semantics about objectNumber (no format rules, no lookup guidance), making the baseline 3 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 ('Opens an interactive deep-zoom viewer') with a clear effect on the user's environment, and explicitly contrasts itself with siblings (inspect_artwork_image for bytes, list/summary/count requests). An agent can distinguish it from remount_viewer/navigate_viewer and the search/detail tools 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 ('when they ask to see, show, or view an artwork'), when-not ('not for list, summary, count, or text-only requests'), and a named alternative for the adjacent case ('use inspect_artwork_image to get image bytes'). Routing is unambiguous.

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

Deploy Server