Clevelandart

Search

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

Input Schema

Name	Required	Description
`cc0`	No	Restrict to CC0-licensed images.
`skip`	No	Offset (default 0)
`type`	No	e.g. "Painting", "Sculpture", "Drawing"
`limit`	No	1-1000 (default 25)
`query`	No	Free-text search across title/description/artist.
`artist`	No
`has_image`	No	Restrict to artworks with a web image.

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedMay 24, 2026

addedInput schema / examples

Added value: +[
+  {
+    "has_image": true,
+    "limit": 25,
+    "query": "portrait",
+    "type": "Painting"
+  },
+  {
+    "artist": "Monet",
+    "cc0": true,
+    "limit": 50,
+    "query": "impressionist landscape"
+  }
+]

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "description": "Search results for artworks from Cleveland Museum of Art",
+  "type": "object"
+}

First observedMay 13, 2026

TDQS

A3.9/5.0

Behavior4/5

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

Annotations already provide readOnlyHint, openWorldHint, idempotentHint, and destructiveHint=false, so the tool's safety is clear. The description adds that filters are optional, which is useful but not essential behavioral context.

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?

The description is a single short sentence that front-loads the core action and lists filters. Every word is meaningful with no redundancy.

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?

While there is an output schema, the description omits important parameters like 'query' and pagination (skip, limit). It covers only a subset of filters, leaving out core search functionality. More detail would improve completeness.

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 documents parameters well. The description only lists some filters (type, artist, has_image, cc0) without adding new meaning beyond the schema. Baseline 3 is appropriate.

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 the verb 'Search' and the resource 'artworks', listing optional filters. It distinguishes its purpose from sibling tools like 'search_within' by focusing on artworks.

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 mentions optional filters but provides no guidance on when to use this tool versus alternatives like 'search_within' or other search tools. No exclusions or context are given.

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

All Clevelandart tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.