Skip to main content
Glama
kintopp

rijksmuseum-mcp+

by kintopp
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

List Curated Sets

list_curated_sets
Read-onlyIdempotent

Browse thematic sets curated by Rijksmuseum staff, including sub-collections like drawings and paintings. Filter by name or member count to find the right scope.

Instructions

Browse thematic sets curated by Rijksmuseum staff. Includes sub-collection groupings (drawings, paintings, iconographic sets). Each result carries memberCount, top dominantTypes, top dominantCenturies by membership, and a category heuristic (object_type / iconographic / album / sub_collection / umbrella) so you can pick the right scope. Use minMembers: 100, maxMembers: 200000 to avoid umbrella sets when the user wants a substantive subset. Pair with browse_set(setSpec) to enumerate members. Not for keyword search across artworks — use search_artwork. Not for aggregate counts — use collection_stats.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
queryNoFilter sets by name (case-insensitive substring match). E.g. 'painting', 'Rembrandt', 'Japanese'
sortByNoSort order: 'name' (alphabetical, default), 'size' (smallest first), 'size_desc' (largest first).
maxMembersNoFilter to sets with at most this many members. Use ~100,000 to exclude umbrella sets like 'Alle gepubliceerde objecten' (834K) and 'Entire Public Domain Set' (732K).
minMembersNoFilter to sets with at least this many members.
includeStatsNoInclude memberCount, dominantTypes, dominantCenturies, category. Default true. Set false for the lightweight legacy shape.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
setsYes
errorNo
queryNo
totalSetsYes
filteredFromNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.90.2
    • 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"
  2. First observedv0.90.0

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so the safety profile is covered. The description adds real value beyond that: it enumerates what each result carries (memberCount, dominantTypes, dominantCenturies, category heuristic) and explains the umbrella-vs-subset behavioral distinction via set size, which is not inferable from annotations.

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?

Dense but front-loaded: purpose first, then what results carry, then a usage tip, then exclusions. Every sentence carries information, though the packed middle sentence listing result fields is slightly heavier than the rest.

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?

With an output schema present, return values need not be re-explained, yet the description still orients the agent to result shape and category values. Combined with the explicit sibling routing and min/max member guidance, nothing needed to invoke it correctly is missing.

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 description coverage is 100%, so the baseline is 3, but the description adds operative guidance the schema lacks: specific minMembers/maxMembers values (100/200000) and the rationale (avoiding umbrella sets like 'Alle gepubliceerde objecten'), plus the category heuristic that helps interpret results.

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 ('Browse thematic sets curated by Rijksmuseum staff') and immediately scopes it by naming the sub-collection groupings and returned fields. It also names sibling tools it is not, so an agent can distinguish it from search_artwork, collection_stats and browse_set without opening a 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?

Explicitly gives when-to-use (browsing curated sets, paired with browse_set(setSpec) to enumerate members) and when-not-to-use ('Not for keyword search ... use search_artwork. Not for aggregate counts — use collection_stats'), plus a concrete minMembers/maxMembers tip (100/200000) to avoid umbrella sets.

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

Deploy Server

Other Tools