Skip to main content
Glama

Artic Search Artworks

artic_search_artworks
Read-onlyIdempotent

Search the Art Institute of Chicago collection by keyword. Returns artwork titles, artists, dates, mediums, and image IDs. Use get_artwork to fetch full details.

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "query": "monet water lilies"
    },
    "name": "artic_search_artworks"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoNumber of results to return (1-100, default 10)
queryYesSearch query (e.g., "monet water lilies")

Output Schema

NameRequiredDescriptionDefault
totalYesTotal number of artworks matching the search query
artworksYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare read-only, idempotent, open-world, non-destructive, so the safety profile is fully covered. The description adds the summary-level return shape (titles, artists, dates, mediums, image IDs), though that partially duplicates the output schema; it says nothing about pagination or result ordering, which is the main remaining behavioral gap.

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?

Three short sentences, front-loaded with purpose, then return contents, then the hand-off to the detail tool. No filler and nothing to trim.

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?

With a full output schema, complete parameter descriptions, and rich annotations, the description carries only the burden of purpose and routing, which it does. Minor omissions like default result count and whether results are paginated keep it at 4 rather than 5.

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 both parameters (query, limit with 1-100 range and default 10) are documented in the schema, plus examples. The description adds no syntax, matching, or ranking guidance for the query string, so 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 (search) and resource (the Art Institute of Chicago collection by keyword) and immediately signals the boundary with artic_get_artwork by noting this returns summary fields while get_artwork fetches full details. An agent can distinguish it from the sibling 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 Guidelines4/5

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

Explicitly routes the agent to artic_get_artwork when full details are needed, which is a genuine alternative-selection rule. It lacks an explicit when-not-to-use clause (e.g., known-item lookup by ID should skip search entirely), which keeps it short of a 5.

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.