Skip to main content
Glama

Metmuseum

by io.github.pipeworx-io

Search Artworks

search_artworks
Read-onlyIdempotent

Search The Met's open-access collection by keyword. Optionally filter to objects with images, currently on view, by medium, or by a year range. Returns compact records (title, artist, date, medium, image) hydrated from object detail. Keyless.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
qYesSearch query, e.g. "sunflowers", "Vermeer", "samurai armor".
limitNoHow many matching objects to hydrate with full detail (default 8, max 15).
on_viewNoOnly return objects currently on view in a gallery.
date_endNoEnd year of the date range, e.g. 1800. Must be paired with date_begin.
date_beginNoStart year of the date range, e.g. 1700. Must be paired with date_end.
has_imagesNoOnly return objects that have images (default true).

TDQS

A4.4/5.0
Behavior5/5

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

Annotations already declare readOnly, openWorld, idempotent, non-destructive. Description adds value by stating 'Keyless' (no auth needed) and describing the return format (compact records with title, artist, date, medium, image hydrated from object detail). No contradictions.

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?

Two sentences, no wasted words. Front-loaded with purpose, then optional filters and output. Highly concise and well-structured.

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?

Covers purpose, optional filters, output format, and keyless access. Missing details like default limit, behavior for no results, or pagination, but adequate for a search tool with rich schema descriptions.

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 descriptions cover all parameters (100% coverage), so baseline 3. The description summarizes available filters but adds no new meaning beyond the schema.

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?

Clearly states it searches The Met's open-access collection by keyword, with optional filters. Distinguishes itself from sibling tools like get_artwork (specific artwork retrieval) and list_departments (department listing) by being a general search tool.

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?

Provides clear context for when to use (keyword search, optional filters) and mentions 'Keyless' indicating no authentication needed. However, it does not explicitly state when not to use or compare to alternatives like get_artwork.

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

All Metmuseum toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A3.5/5.0
Disambiguation2/5

The server mixes two Met-specific tools (get_artwork, search_artworks) with a large set of generic Pipeworx tools (ask_pipeworx, bet_research, etc.), making it unclear which tools actually relate to the Met museum. Agents will struggle to distinguish the domain-specific tools from the general data tools.

Naming Consistency2/5

Tool names follow no consistent pattern: Met-specific tools use get_/search_/list_ prefixes, while Pipeworx tools use diverse patterns (ask_, bet_, compare_, discover_) and some use underscores while others lack verbs. The inconsistency increases cognitive load.

Tool Count3/5

At 29 tools, the count is high but not unreasonable for a combined server. However, only 3 tools are Met-specific, so the count feels inflated by unrelated tools. A more focused Met server would have fewer tools.

Completeness2/5

For a Met museum server, the tool surface is severely limited: only search, get by ID, and list departments. Missing operations like filtering by artist, retrieving related objects, or accessing collection highlights. The domain coverage is incomplete.

Resources