Skip to main content
Glama

Clevelandart Search

clevelandart_search
Read-onlyIdempotent

Search artworks. Optional filters: type, artist, has_image, cc0.

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": {
      "type": "Painting",
      "limit": 25,
      "query": "portrait",
      "has_image": true
    },
    "name": "clevelandart_search"
  }
}

Input Schema

NameRequiredDescriptionDefault
cc0NoRestrict to CC0-licensed images.
skipNoOffset (default 0)
typeNoe.g. "Painting", "Sculpture", "Drawing"
limitNo1-1000 (default 25)
queryNoFree-text search across title/description/artist.
artistNo
has_imageNoRestrict to artworks with a web image.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.9/5.0
Behavior2/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false, and openWorldHint, so the safety and idempotency profile is fully covered by structured data. The description adds essentially no behavioral context beyond that — no note on result ordering, pagination behavior, or rate limits — and its filter list largely restates the 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?

Two short, front-loaded clauses with no filler. It is efficient, though so compressed that it reads more like an index entry than a usable definition.

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

Completeness3/5

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

An output schema exists and most parameters are documented in the schema, so the return value needn't be explained. However, for a seven-parameter, zero-required search tool the description leaves key questions open — whether an empty query lists all artworks, and how results are ordered or paged.

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 86%, so the schema already explains query, type, cc0, has_image, limit, and skip. The description's brief filter enumeration ('type, artist, has_image, cc0') adds no meaning beyond those field descriptions and omits skip/limit entirely; baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/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 artworks') and names the filter dimensions, so an agent immediately knows this is a search tool rather than a detail-fetch tool like clevelandart_get_artwork. It stops short of any explicit differentiation from siblings, which keeps it below a 5.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

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

There is no guidance on when to use this tool versus clevelandart_get_artwork or the other search siblings; the only usage statement is that filters are optional. It also doesn't say what happens with no query at all, which matters since there are zero required parameters.

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.