Städel Museum MCP Server

get-museum-object

Retrieve detailed information about a Städel Museum object using its OAI identifier or object number, including metadata and optional high-resolution image.

Instructions

Get detailed information about a specific Städel museum object by its OAI identifier (e.g. oai:DE-MUS-048017:2442) or bare object number (e.g. 2442). Returns metadata and optionally the high-resolution image.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "objectId": "<objectId>"
    },
    "name": "get-museum-object"
  }
}

Input Schema

Name	Required	Description	Default
`objectId`	Yes	The OAI identifier (e.g., oai:DE-MUS-048017:2442) or bare object number
`returnImage`	No	Whether to return the image (if available) as base64

Output Schema

Name	Required	Description	Default
`object`	Yes	Detailed object data mapped from LIDO metadata

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Jul 30, 2026

TDQS

A4/5.0

Behavior3/5

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

No annotations are provided, so the description is the sole source. It discloses the return includes metadata and optionally a base64 image, but does not detail potential errors, authentication requirements, or the extent of 'detailed information'. Adequate but not comprehensive.

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?

The description is two sentences long, front-loaded with the main action, and contains no extraneous words.

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?

Given the simple tool with only two parameters and an existing output schema, the description adequately covers the input format and return behavior. It could mention potential error responses, but overall it is sufficient for an agent to use correctly.

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

Parameters3/5

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

Schema coverage is 100% and the description adds minimal new information beyond the parameter descriptions, except mentioning that the image is returned as base64. The description does not elaborate on the objectId format beyond what the schema says.

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 fetches detailed information for a single Städel museum object using an OAI identifier or bare number, distinguishing it from sibling tools like 'search-museum-objects' and 'list-sets'.

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?

The description specifies the input format (OAI identifier or bare object number) and the optional return of an image. It implies usage when you have a specific object ID, but does not explicitly contrast with siblings or mention when to avoid using it.

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

Deploy Server