Skip to main content
Glama
kintopp

rijksmuseum-mcp+

by kintopp

Get Artwork Bibliography

get_artwork_bibliography
Read-onlyIdempotent

Fetch scholarly citations and references for a specific artwork using its object number. Returns publication details like ISBN and pages, with a total count or full list of entries.

Instructions

Scholarly references for ONE artwork by objectNumber: citations, with linked publication, pages, ISBN where known. Follows a search_artwork / get_artwork_details result. By default returns the first 5 plus a total count; set full=true for all entries (major works can have 100+ — mind the context window). Not for general metadata — use get_artwork_details. Not for library-catalogue search.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
fullNoIf true, return ALL entries (may be 100+). Default: first 5 + total count.
objectNumberYesThe object number of the artwork (e.g. 'SK-C-5').

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
errorNo
totalYesTotal citations for the artwork (full count, even when only the first few entries are returned).
entriesYesScholarly references for the artwork. Empty when none were harvested.
warningsNo
objectNumberYes
Behavior5/5

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

Discloses default pagination (first 5 + total count), the full=true option, and warns about large context windows, adding significant behavioral context beyond the readonly and idempotent 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?

Three sentences with no wasted words; front-loaded with purpose, followed by usage context and a key caveat. Every sentence earns its place.

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?

Covers what is returned, usage context, default pagination, and warnings. With an output schema present, no need to detail return format. Complete for the tool's complexity.

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

Parameters4/5

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

Schema coverage is 100%, but description adds practical context: the default behavior for 'full' parameter and a warning about context window, going beyond the schema description.

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 it provides scholarly references for one artwork by objectNumber, and distinguishes from siblings by stating what it is not for (general metadata or library-catalogue search).

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 says it follows a search_artwork/get_artwork_details result, and lists exclusion cases (not for general metadata, not for library-catalogue search), providing clear when-to-use and when-not-to-use guidance.

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