Skip to main content
Glama

art-institute-chicago-mcp-server

Search exhibitions

artic_search_exhibitions
Read-onlyIdempotent

Search Art Institute of Chicago exhibitions by text, date, artwork_id, or artist_id. Relationship filters cover recorded museum links; an absent link does not prove an artwork or artist never appeared in a show. For the full exhibition record of one artwork, read the exhibition_history section of artic_get_artworks. Results carry dates, gallery, summary, web page, and listed artworks. Pass artwork ids to artic_get_artworks for full records.

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": "artic_search_exhibitions"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNoPage to return (1-based); page times the applied limit may not exceed 1,000.
sortNorelevance ranks by query text; start_desc and start_asc sort by opening date. Defaults to relevance with a query, else start_desc; relevance without a query sorts as start_desc.
whenNocurrent: open today; upcoming: opens after today; past: closed before today; any: no date condition. A show with no recorded closing date is past when marked Closed, else current from its opening.any
limitNoRequested exhibitions per page (1-1,000); at most 100 are returned.
queryNoText matched against exhibition titles, descriptions, and other fields; every word must match, except common English words such as the and of, which are ignored.
date_toNoLatest date, YYYY-MM-DD; an exhibition matches when its run overlaps date_from to date_to. Missing dates are read as described for date_from.
artist_idNoExact museum agent id, from artic_search_artists or an artwork artist_id; matches recorded exhibition relationships. Combined with every other condition using AND.
date_fromNoEarliest date, YYYY-MM-DD; an exhibition matches when its run overlaps date_from to date_to. A show with no recorded closing date ran on its opening date alone when marked Closed, else runs on from its opening; one with only a closing date ran on that date alone; one with no dates matches no window.
artwork_idNoExact museum artwork id, from artic_search_artworks or artic_get_artworks; matches recorded exhibition relationships. Combined with every other condition using AND.

Output Schema

NameRequiredDescriptionDefault
capNoThe limit applied to this page.
pageNoPage returned (1-based).
errorNoPresent when the call failed. Absent on success.
shownNoExhibitions returned on this page.
noticeNoGuidance when nothing matched, more pages exist, or the reachable window is exhausted.
has_moreNoTrue when more matches exist beyond this page.
next_pageNoPage to request next; absent when nothing remains or the next page would pass the first 1,000 matches.
truncatedNoTrue when more matches exist beyond this page.
totalCountNoMatches for the query and filters, before paging.
exhibitionsNoMatching exhibitions on this page, in ranked or sorted order.
license_textNoLicense statement from the API for this data, verbatim.
sort_appliedNoOrder applied.
when_appliedNoThe when condition applied.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed7 schema fields changed
    • changedInput schema / properties / date_from / description
      Previous value: -"Earliest date, YYYY-MM-DD; an exhibition matches when its run overlaps date_from to date_to."New value: +"Earliest date, YYYY-MM-DD; an exhibition matches when its run overlaps date_from to date_to. A show with no recorded closing date ran on its opening date alone when marked Closed, else runs on from its opening; one with only a closing date ran on that date alone; one with no dates matches no window."
    • changedInput schema / properties / date_to / description
      Previous value: -"Latest date, YYYY-MM-DD; an exhibition matches when its run overlaps date_from to date_to."New value: +"Latest date, YYYY-MM-DD; an exhibition matches when its run overlaps date_from to date_to. Missing dates are read as described for date_from."
    • changedInput schema / properties / limit / description
      Previous value: -"Requested exhibitions per page (1-1,000); at most 25 are returned."New value: +"Requested exhibitions per page (1-1,000); at most 100 are returned."
    • changedInput schema / properties / query / description
      Previous value: -"Text matched against exhibition titles, descriptions, and other fields; every word must match."New value: +"Text matched against exhibition titles, descriptions, and other fields; every word must match, except common English words such as the and of, which are ignored."
    • changedInput schema / properties / when / description
      Previous value: -"current: open today; upcoming: opens after today; past: closed before today; any: no date condition."New value: +"current: open today; upcoming: opens after today; past: closed before today; any: no date condition. A show with no recorded closing date is past when marked Closed, else current from its opening."
    • changedOutput schema / properties / exhibitions / items / properties / end / description
      Previous value: -"Closing date and time, ISO 8601 with offset."New value: +"Closing date and time, ISO 8601 with offset; absent when not recorded. A show without one counts as closed after its opening date when marked Closed, else as still running from its opening."
    • changedOutput schema / properties / exhibitions / items / properties / start / description
      Previous value: -"Opening date and time, ISO 8601 with offset."New value: +"Opening date and time, ISO 8601 with offset; absent when not recorded. A show without one is never current or upcoming, and date windows match it on its closing date alone."
  2. Changed7 schema fields changed
    • addedInput schema / properties / artist_id
      Added value: +{
      +  "description": "Exact museum agent id, from artic_search_artists or an artwork artist_id; matches recorded exhibition relationships. Combined with every other condition using AND.",
      +  "exclusiveMinimum": 0,
      +  "maximum": 9007199254740991,
      +  "type": "integer"
      +}
    • addedInput schema / properties / artwork_id
      Added value: +{
      +  "description": "Exact museum artwork id, from artic_search_artworks or artic_get_artworks; matches recorded exhibition relationships. Combined with every other condition using AND.",
      +  "exclusiveMinimum": 0,
      +  "maximum": 9007199254740991,
      +  "type": "integer"
      +}
    • changedInput schema / properties / limit / description
      Previous value: -"Exhibitions per page (1-25)."New value: +"Requested exhibitions per page (1-1,000); at most 25 are returned."
    • changedInput schema / properties / limit / maximum
      Previous value: -25New value: +1000
    • changedInput schema / properties / page / description
      Previous value: -"Page to return (1-based, 1-40); page times limit may not exceed 1,000."New value: +"Page to return (1-based); page times the applied limit may not exceed 1,000."
    • changedInput schema / properties / page / maximum
      Previous value: -40New value: +1000
    • changedOutput schema / properties / error / properties / data / properties / reason / description
      Previous value: -"Machine-readable failure mode. Declared by this tool: `invalid_date_range`: date_from is later than date_to. `page_beyond_window`: The API refused the page as past the first 1,000 matches (the page and limit bounds keep calls inside it). `rate_limited`: The Art Institute API throttled this server and retries ran out, or the shared request queue could not start the call in time. `request_blocked`: The Art Institute API's firewall blocked the request, as it does for markup or script-like text and for bursts of traffic. `upstream_rejected_query`: The Art Institute API rejected a request this server built from valid inputs. Other values are possible when a failure originates below the handler."New value: +"Machine-readable failure mode. Declared by this tool: `invalid_date_range`: date_from is later than date_to. `page_beyond_window`: page times the applied limit exceeds 1,000, past the reachable search window. `rate_limited`: The Art Institute API throttled this server and retries ran out, or the shared request queue could not start the call in time. `request_blocked`: The Art Institute API's firewall blocked the request, as it does for markup or script-like text and for bursts of traffic. `upstream_rejected_query`: The Art Institute API rejected a request this server built from valid inputs. Other values are possible when a failure originates below the handler."
  3. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, and openWorld, so the safety profile is covered. The description adds a genuinely useful data-completeness caveat: 'an absent link does not prove an artwork or artist never appeared in a show,' which no annotation conveys. The sentence listing returned fields is largely redundant with the existing output schema.

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?

Front-loaded with the verb, resource, and filter axes, then the caveat, then the alternative route. Every sentence is purposeful except the results-field inventory, which restates what the output schema already documents and could be dropped.

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?

Nine optional parameters, an output schema, and full annotation coverage mean the description need not restate schema detail, and it doesn't. It covers purpose, the key interpretive caveat, and the follow-up handoff; only minor gaps remain, such as when to prefer a plain date sweep over a text query.

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 parameter descriptions are detailed (overlap semantics, enum meanings, AND combination), so the schema does the heavy lifting. The description reinforces that relationship filters operate on recorded links only, which adds some meaning beyond the schema, but it gives no format or default guidance the schema lacks. Baseline 3 applies.

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 ('Search Art Institute of Chicago exhibitions') and names the four filter axes (text, date, artwork_id, artist_id), which lets an agent distinguish it from artic_search_artworks and artic_search_artists without opening a schema.

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 routes the agent: 'For the full exhibition record of one artwork, read the exhibition_history section of artic_get_artworks,' and it explains the follow-up chain ('Pass artwork ids to artic_get_artworks for full records'). It also warns when the relationship filters are not conclusive, which is precisely the decision point an agent faces.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.