Fireside Folio

Search the museum

search_museum

Read-only

Search hundreds of thousands of public-domain artworks from The Met, the Art Institute of Chicago, the National Gallery of Art, the Rijksmuseum, the Cleveland Museum of Art and SMK (Denmark): paintings, prints, drawings, photographs, maps, manuscripts, sculpture and more. Use a room for a curated theme. Returns a ref for each work.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "search_museum"
  }
}

Input Schema

Name	Required	Description
`era`	No
`kind`	No
`page`	No
`room`	No	A curated room: impressionists, post-impressionists, dutch-golden-age, renaissance, durer-and-prints, ukiyo-e, china, india-persia, egypt, greece-rome, medieval, manuscripts, portraits, landscapes, still-life, botanical, birds, cats-dogs, horses, sea, winter, night, myths, cities, maps, early-photography, posters, danish-golden-age, arms, fashion, africa-americas.
`query`	No	Artist, title or subject ("Hokusai", "sunflowers", "ships in a storm").
`museum`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 12, 2026

TDQS

A3.5/5.0

Behavior3/5

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

Annotations already declare readOnlyHint, destructiveHint=false and openWorldHint=false, so safety is covered. The description adds genuine value by stating scope (public-domain works across six institutions) and the return shape ('Returns a ref for each work') in the absence of an output schema, but says nothing about result counts, pagination limits, or rate behavior.

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?

Three sentences, front-loaded with the collection scope, then a usage hint, then the return value. The museum list is long but informative; 'and more' is minor filler. Nothing is redundant or buried.

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

Completeness3/5

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

For a six-parameter, all-optional search tool with no output schema, the definition covers scope and return type but leaves the agent guessing about pagination, default result size, and whether filters are combinable. It is usable but not fully self-sufficient.

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 only 33%, so the description has to compensate, and it does partially: it spells out the six museums corresponding to the opaque enum keys (met, aic, nga, rijks, cma, smk) and clarifies the abstract 'room' concept as curated themes, plus the enumerated media map onto 'kind'. Era, page, and query format remain undocumented, and the page cap of 50 is never explained.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names a specific verb (search) and a precisely scoped resource: public-domain artworks from six named museums, with enumerated medium types. An agent can tell this is an art-collection search rather than a library or encyclopedia search, though it never explicitly contrasts itself with those siblings.

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

Usage Guidelines3/5

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

The line 'Use a room for a curated theme' is the only usage instruction, and it usefully hints at browsing-by-theme behavior. There is no guidance on when to prefer query vs. room vs. filters, no exclusion cases, and no mention of alternatives.

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

All Fireside Folio tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?