Skip to main content
Glama
kintopp

rijksmuseum-mcp+

by kintopp

List Curated Sets

list_curated_sets
Read-onlyIdempotent

Browse curated thematic sets from the Rijksmuseum, filtered by name and size. Each set shows member count, dominant artwork types, centuries, and a category to select the right scope.

Instructions

Browse thematic and sub-collection groupings curated by Rijksmuseum staff (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
Behavior4/5

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

Annotations already declare read-only, idempotent, non-destructive. Description adds rich behavioral context about result shape (category heuristic, memberCount) and pairing with browse_set. No contradictions. Minor gap: no mention of pagination or rate limits, but sufficient given 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?

Single concise paragraph with front-loaded purpose. Every sentence adds value: purpose, result details, usage tip, pair suggestion, exclusions. No redundancy.

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 5 parameters, 1 enum, and presence of output schema, the description covers purpose, usage scenarios, result attributes, parameter tips, and sibling relationships comprehensively. Adequate for an AI agent to correctly select and invoke.

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 baseline is 3. Description adds operational guidance beyond schema, e.g., using minMembers/maxMembers to filter umbrella sets and examples for query parameter, justifying a 4.

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 browses thematic and sub-collection groupings curated by staff, listing specific result attributes (memberCount, dominantTypes, etc.) and distinguishing from sibling tools like browse_set, search_artwork, and collection_stats.

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 provides when to use (for thematic groupings) and when not (for keyword search or aggregate counts). Includes practical advice on parameter values (minMembers/maxMembers) 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.

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