Skip to main content
Glama
mildlydiverting

whitney-museum-mcp-server

Search Whitney audio guides

whitney_search_guides
Read-onlyIdempotent

Find Whitney Museum audio guides published since 2009. Search by title or filters, and retrieve guide stops for each result.

Instructions

Search audio guides published since 2009. Fetching an individual guide also returns its stops.

Args:

  • title (string, optional), filters (object, optional), sort (string, optional)

  • page (number, default 1), limit (number, 1-30, default 10)

  • response_format ('markdown' | 'json', default 'markdown')

Returns: { total, count, page, has_more, next_page?, results[] }

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pageNo1-based page number; the API returns 30 records per page
sortNoRansack sort string, e.g. 'start_time desc', 'title asc', or 'random'
limitNoMaximum records to return from the fetched page (1-30). Keep this low unless you need the detail — Whitney records are verbose.
titleNoWords appearing in the title
filtersNoRaw Ransack predicates, e.g. { "title_cont": "moon", "classification_eq": "Paintings" }. Matchers: _eq, _not_eq, _cont, _not_cont, _cont_all_split, _true, _false, _gt, _gteq, _lt, _lteq.
response_formatNoOutput format: 'markdown' for reading, 'json' for machine processingmarkdown

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
noteNoAdvisory note about trimming or pagination
pageYesPage that was fetched
countYesRecords returned in this response
totalYesTotal matching records across all pages
sourceYesAttribution for the data, as the Whitney's terms ask for
resultsYesThe records
has_moreYesWhether further pages exist
next_pageNoPage number to request next

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4/5.0
Behavior4/5

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

Annotations already cover read-only, idempotent, and non-destructive behavior. The description adds useful context beyond those annotations: guides are limited to those published since 2009, and fetching an individual guide also returns its stops. This gives the agent concrete expectations about scope and result contents.

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 compact and well-structured, with the core purpose stated first. The Args and Returns summaries are concise and easy to scan, with no filler or repetition of the schema's full descriptions.

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?

The description covers the resource, temporal scope, result shape, pagination fields, and parameter defaults, which is sufficient for most search calls. It falls slightly short only on explicit guidance about choosing this tool over sibling searches.

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 description coverage is 100%, so the schema already documents all six parameters thoroughly, including defaults, ranges, and Ransack syntax. The description's Args list is a useful summary but adds no new semantic information beyond what the schema provides.

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 states a specific verb and resource: 'Search audio guides', and adds a meaningful scope constraint ('published since 2009'). It is clearly distinguishable from sibling search tools (events, artworks, artists, exhibitions) because the resource type is explicit.

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 description makes it clear this tool is for searching audio guides, but it does not explicitly explain when to prefer this over sibling tools like whitney_search_artworks or whitney_query. There are no excluded cases or alternative tool recommendations.

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