Skip to main content
Glama
kintopp

rijksmuseum-mcp+

by kintopp

Inspect Artwork Image

inspect_artwork_image
Read-onlyIdempotent

Provides image data for AI visual analysis of an artwork or region, allowing detailed inspection of inscriptions, details, or multi-panel works using percentage or pixel coordinates.

Instructions

Returns image bytes (base64) for the LLM's own visual analysis of an artwork or region. The LLM can see and reason about the image immediately — not for the user to view (use get_artwork_image for the interactive viewer). Not for listing or summarising artworks — use search_artwork.

Use with region 'full' (default) to inspect the complete artwork, or specify a region to zoom into details, read inscriptions, or examine specific areas. The response includes cropPixelWidth/cropPixelHeight: the actual pixel dimensions of the returned image.

Region coordinates: 'pct:x,y,w,h' (percentage of full image, recommended), 'crop_pixels:x,y,w,h' (pixel coordinates of the full image — use with nativeWidth/nativeHeight from a prior response), or 'x,y,w,h' (legacy IIIF pixels, equivalent to crop_pixels). Quick reference:

  • Top-left quarter: pct:0,0,50,50

  • Bottom-right quarter: pct:50,50,50,50

  • Center strip: pct:25,25,50,50

  • Full image: full (default)

  • For multi-panel works: use physical dimensions from get_artwork_details to estimate panel percentages, then inspect individual panels with close-up crops.

Iterative zoom: start with region 'full' to understand the layout, then use close-up crops (600–800px) to read specific features. When a viewer is open for this artwork, it automatically zooms to the inspected region (navigateViewer defaults to true, no effect when region is 'full'), keeping the viewer in sync with your analysis — no separate navigate_viewer call needed for basic zoom.

The response includes the active viewUUID (if any) for follow-up navigate_viewer calls.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
sizeNoWidth of returned image in pixels (200–2016, default 1568). Defaults align to multiples of 28 for clean LLM coordinate handling: 1568 is Sonnet 4.6's native resolution cap, 2016 is the highest ×28 multiple that stays within Opus 4.7's per-image token budget across common aspect ratios.
regionNoIIIF region: 'full', 'square', 'pct:x,y,w,h' (percentage), 'crop_pixels:x,y,w,h' (pixels of the full image — use with nativeWidth/nativeHeight from a prior response), or 'x,y,w,h' (legacy IIIF pixels, equivalent to crop_pixels). E.g. 'pct:0,60,40,40' for bottom-left 40%.full
qualityNoImage quality — 'gray' can help read inscriptions or signaturesdefault
rotationNoClockwise rotation in degrees
viewUUIDNoTarget a specific viewer session (from get_artwork_image). When omitted, auto-discovers a viewer for this artwork.
objectNumberYesThe object number of the artwork (e.g. 'SK-C-5')
navigateViewerNoAuto-navigate the open viewer to the inspected region (default: true). Only effective when a viewer is open for this artwork.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
errorNo
titleNoArtwork title — mirrors the caption in the text/image channel so structuredContent readers retain it.
regionYes
creatorNoArtwork creator — mirrors the caption in the text/image channel.
qualityYes
rotationYes
viewUUIDNoActive viewer session ID (if a viewer is open for this artwork)
cropRegionNoNormalized IIIF region used for the fetch; crop_pixels: inputs are normalized to plain IIIF pixel regions.
fetchTimeMsNoTime spent fetching from IIIF server (ms)
nativeWidthNo
nativeHeightNo
objectNumberYes
requestedSizeYes
cropPixelWidthNoActual width in pixels of the returned inspect image/crop. Use with cropPixelHeight for crop-local pixel overlays.
regionRecoveryNoOut-of-bounds recovery hint. Present only on an `overlay_region_out_of_bounds` error — mirrors the recovery payload that the text channel renders, so a structuredContent reader can self-correct without parsing prose.
cropPixelHeightNoActual height in pixels of the returned inspect image/crop. Use with cropPixelWidth for crop-local pixel overlays.
viewerNavigatedNoWhether the viewer was auto-navigated to the inspected region
Behavior5/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false. The description adds context: base64 return, crop dimensions in response, and viewer navigation behavior without contradiction.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Well-structured with clear paragraphs, but slightly lengthy. Front-loaded core purpose. Each sentence adds value, but could be tightened.

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?

Given 7 parameters and output schema, the description covers all aspects: region types, size constraints, quality use cases, viewer integration, and multi-panel handling.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, but the description adds significant value: explains region formats with examples, size rationale (28 multiples for LLM), quality 'gray' for inscriptions, and iterative zoom strategy.

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 the tool returns image bytes for LLM visual analysis, distinguishing it from get_artwork_image (for users) and search_artwork (for listing). The verb 'inspect' with object 'artwork image' is specific and informative.

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?

Explicitly states when NOT to use the tool (use get_artwork_image for user viewing, search_artwork for listing). Provides detailed guidance on region selection, iterative zoom strategy, and viewer synchronization.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/kintopp/rijksmuseum-mcp-plus'

If you have feedback or need assistance with the MCP directory API, please join our Discord server