get_exhibition
Read-only
Get one exhibition by slug: description, curator, organizers, participating artists, works shown, and verified press reception.
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| slug | Yes |
arhiiv
by ee.ehtekunst
TDQS
A4/5.0
Behavior3/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint and openWorldHint. The description adds the return fields but does not disclose additional behaviors (e.g., error handling, permissions). No contradiction.
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?
Single sentence of 16 words, front-loaded with the action and resource, no unnecessary 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 no output schema, the description lists all returned fields. The tool is simple (one param, no nesting). Could mention error behavior, but adequate for the complexity.
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?
The single parameter 'slug' has no schema description (0% coverage). The description compensates by indicating it's an identifier for the exhibition, adding essential meaning.
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 it retrieves an exhibition by slug and lists the fields returned (description, curator, etc.), distinguishing it from sibling tools like search_exhibitions and get_artist.
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 implies use when you have a specific slug but provides no explicit guidance on when to use versus alternatives like search_exhibitions, and no contraindications.
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.
TDQS
A4.2/5.0
Disambiguation5/5
Each tool targets a unique entity or action (e.g., get_artist vs. search_artists, get_relations vs. get_stats). No two tools have overlapping purposes, so an agent can clearly distinguish them.
Naming Consistency5/5
All tools follow a consistent verb_noun pattern: either get_<entity> or search_<entity>. No mixing of conventions like camelCase or different verbs.
Tool Count5/5
12 tools is well-scoped for an archive server covering artists, exhibitions, works, organizations, marks, press, and graph relations. Each tool earns its place without redundancy.
Completeness5/5
The tool surface covers the main entities (artists, works, exhibitions, organizations) and provides search and retrieval for all key types. Additional tools like get_relations and get_timeline fill gaps for connected data and chronology, making the set feel complete for its domain.