Skip to main content
Glama
kintopp

rijksmuseum-mcp+

by kintopp
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Find Artworks Citing a Publication

find_artworks_citing_publication
Read-onlyIdempotent

Find artworks that cite a given publication URI or ID; returns citing works and total count for reverse bibliography lookups.

Instructions

Reverse bibliography: artworks citing a given publication URI or id. Use the publicationUri from get_artwork_bibliography (e.g. 'https://id.rijksmuseum.nl/301154354') or the bare id. Local and resolver-free. Not for topic search of the library catalogue.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
fullNoIf true, return ALL citing artworks. Default: first 20 + total count.
publicationYesPublication URI (https://id.rijksmuseum.nl/301…) or the bare publication id.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
errorNo
totalYes
artworksYesArtworks whose bibliography cites this publication. Empty when none (or bibliography not harvested).
warningsNo
publicationIdYes
publicationUriYes

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. Changed2 schema fields changedv0.90.1
    • removedOutput schema / properties / artworks / items / properties / creator / anyOf
      Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
    • addedOutput schema / properties / artworks / items / properties / creator / type
      Added value: +[
+  "string",
+  "null"
+]
  3. First observedv0.90.0

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, and non-open-world behavior; the description reinforces this by stating the lookup is 'local and resolver-free', which tells the agent no network resolution is needed. It does not mention the default 20-item cap or total-count behavior, though that is covered in the schema's `full` parameter.

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 short clauses, front-loaded with the core purpose, then input source, then exclusion. No filler.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With annotations covering safety semantics and an output schema covering returns, the description only needs to explain what the tool does and what to feed it – both present. The pagination default is left to the schema, which is acceptable.

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%, so the baseline is 3, but the description adds real value beyond the schema by giving a concrete example URI and explaining that a bare publication id is also accepted.

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 and resource ('artworks citing a given publication URI or id') and frames it as a 'reverse bibliography', which immediately distinguishes it from the forward-direction sibling get_artwork_bibliography. An agent can pick correctly without opening either schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives explicit input provenance ('Use the publicationUri from get_artwork_bibliography') and one exclusion ('Not for topic search of the library catalogue'). The exclusion references something outside the sibling list, so it is less useful than naming a sibling tool would be, but the positive routing is clear.

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