Skip to main content
Glama

Search artworks

search_artworks
Read-onlyIdempotent

Search the catalogue of moving-image works by César Yagüe by free text, collection, resolution, orientation (including ultrawide), colour measured from every frame (a basic colour counts its whole family), price, year, loop length, rotation and availability. A short page brings each work's curatorial capsule. Asking about flashes or epilepsy returns the works with measured abrupt light events.

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

Input Schema

NameRequiredDescriptionDefault
yearNoYear the work was created
limitNo
orderNo
queryNoFree text across titles, descriptions and curatorial notes
colourNoDominant colour by name (gold, teal, crimson…) or hex. Measured from every frame.
offsetNoSkip this many results, to read the next page
sort_byNo
rotationNoWhether the work must keep its orientation or may be rotated 90 degrees
max_priceNo
min_priceNo
collectionNoCollection name
resolutionNoThe resolution label each work shows, matched exactly: HD, 4K, 5K, 8K, 10K, 12K, 16K; square works carry their own, such as 2K or 3K. An unknown label returns the list in use.
max_secondsNoLongest loop length, in seconds
min_secondsNoShortest loop length, in seconds
orientationNoultrawide = at least twice as wide as tall (21:9 and wider); landscape includes it
availabilityNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds real behaviour beyond that: results arrive as a short page whose entries carry a curatorial capsule, flash/epilepsy queries return works with measured abrupt light events, and an unknown resolution label returns the list in use.

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 sentences, front-loaded with the verb and target, with a second that front-loads the output shape and the special-query behaviour. The middle filter enumeration is dense and partly restates schema enum names, which costs a little.

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?

For a 16-parameter, no-required-parameter search with no output schema, the definition conveys the result shape (paged list with curatorial capsule) and the notable special cases. It stops short of stating how multiple facets combine or what the default page size and ordering are, which an agent would still have to guess.

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?

Schema coverage of 63% leaves undocumented parameters (limit, order, sort_by, min/max price, availability), and the description compensates by naming the full filter set. It also adds genuine semantics absent from the schema, notably that a basic colour counts its whole family and that orientation includes ultrawide.

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?

Specific verb ('Search') and resource ('catalogue of moving-image works by César Yagüe') with an enumeration of the searchable dimensions. It is clearly a multi-facet catalogue query, distinguishable in substance from get_artwork or browse_collections, though no sibling is named explicitly.

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?

Usage is only implied by the facet list; there is no statement of when to prefer this over rank_artworks, recommend_for_space, or browse_collections, nor any exclusion. The one genuinely usage-shaped hint is the epilepsy/flashes query behaviour, which tells the agent a natural-language safety question is handled here.

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.

Resources