Skip to main content
Glama

skkg_search_exhibitions

skkg_search_exhibitions
Read-onlyIdempotent

Find SKKG exhibition records by title, venue, year range, type, status, or featured object. Retrieve each exhibition's dates, venues, object counts, and website link.

Instructions

Search the exhibitions SKKG records, by title, venue, year, type, and object. Most of them showed objects of the collection. A touring exhibition is often one record whose other venues are its stations, each with its own dates and status. Filters: query (words of the title and the venues), venue (the main venue or another station, never a cancelled one), a year range (by the dates of any station; with venue, of the station at that venue), exhibition_type, status, internal_external (SKKG's "intern" or "extern"), and includes_object. Without a filter, lists every exhibition. Each result gives its type, status, dates, venue, other venues with their status and dates, object_count, literature_count, and website_url. For one exhibition with its objects, literature, and images, use skkg_get_record with its id; for its objects as search rows, skkg_search_objects with exhibition; for the terms the term filters take, skkg_find_terms with vocabulary "exhibition_type", "exhibition_status", or "internal_external".

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

Input Schema

NameRequiredDescriptionDefault
langNoLanguage of vocabulary labels. Most vocabularies, materials and object types among them, have German labels only, which are returned whatever the language; titles and texts stay as recordedde
sortNorelevance (the default with `query`), date_asc (the default without; undated last), date_desc (by the end, undated last), or title
limitNoExhibitions per page. Default 10
queryNoWords of the title or of a venue's name or place, e.g. "Hodler", "Giacometti Zürich"; the venues include cancelled stations. Every word must occur; "a phrase" matches in order; a trailing * matches a prefix; OR between two words matches either; NOT before a word excludes it
venueNoVenue: a name, e.g. "Kunsthaus Zürich", a place, e.g. "Winterthur", or an address id from a result. Each word matches the start of a word of the venue's name and place, ignoring case and accents. Matches the main venue and the other stations, but no station SKKG cancelled ("abgesagt"); applied_filters lists the venues matched
offsetNo
statusNoSKKG's status of the exhibition, e.g. "aktuell", "abgeschlossen", "historisch". A term id ("type/…") or a German label, matched exactly except for case.
year_toNoLatest year; see year_from
year_fromNoEarliest year: an exhibition matches when the dates of one of its stations overlap the range (with venue, those of the station at that venue); one without a venue, by its own dates. One with only a start date matches its start year only, also a current one (status "aktuell"); undated ones never match
exhibition_typeNoKind of exhibition, e.g. "Einzelausstellung", "Wechselausstellung", "Wanderausstellung", "Dauerausstellung". A term id ("type/…") or a German label, matched exactly except for case.
includes_objectNoObject id or inventory number: the exhibitions that showed it
internal_externalNoSKKG's "intern" or "extern". A term id ("type/…") or a German label, matched exactly except for case.

Output Schema

NameRequiredDescriptionDefault
sortYes
totalYesExhibitions that match
offsetYes
resultsYes
has_moreYes
returnedYes
warningsNo
data_as_ofNo
next_offsetNo
applied_filtersNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.5.0

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare read-only, idempotent, closed-world, non-destructive behaviour, so the bar is lower. The description still adds real model knowledge beyond them: a touring exhibition is one record whose other venues are stations with their own dates and status, and a cancelled station is never matched by `venue`. It does not discuss pagination behaviour beyond the `limit` parameter, which keeps it short of a 5.

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?

Purpose and scope lead, then domain context, then the alternatives block, so it is front-loaded and navigable. Some of the filter enumeration duplicates the schema descriptions and could be trimmed without losing information.

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

Completeness5/5

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

For a 12-parameter, all-optional search tool with an output schema, the description supplies the data model (touring records and stations), the routing to three sibling tools, and the unfiltered default. Nothing an agent needs to invoke it correctly is missing.

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 92%, so the schema already carries nearly all parameter meaning, including the station/date matching rules for `year_from`/`year_to`. The description restates the filter list rather than adding syntax or format detail the schema lacks, which is the expected baseline.

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?

"Search the exhibitions SKKG records, by title, venue, year, type, and object" states a specific verb and resource plus the searchable facets, so the agent can distinguish it from skkg_search_objects 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 Guidelines5/5

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

Gives explicit routing rules: no filter lists everything; a single exhibition with objects, literature and images goes to skkg_get_record; object rows go to skkg_search_objects with `exhibition`; term vocabularies go to skkg_find_terms with named vocabulary values. This names alternatives and the conditions that select them.

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