Skip to main content
Glama

met_search

Read-onlyIdempotent

Search the Metropolitan Museum of Art collection for artworks by keyword, optionally limiting results to objects with images.

Instructions

Search the Metropolitan Museum of Art collection for artworks.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "query": "<query>"
    },
    "name": "met_search"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryYesSearch query (e.g. sunflowers, Egyptian, armor)
hasImagesNoOnly return objects with images (default true)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.1.11

TDQS

C2.9/5.0
Behavior2/5

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

Annotations already declare readOnly, idempotent, non-destructive and openWorld, so the safety profile is covered. The description adds nothing beyond that — no note on result limits, pagination, whether matching is keyword or fuzzy, or how many records come back for a broad query like 'Egyptian'.

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?

One front-loaded sentence with no filler. It is efficient, though arguably under-specified rather than deliberately tight — nothing extra earns its place because nothing extra exists.

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?

For a two-parameter read-only search with a fully documented schema and clear annotations, the essentials are present. But with no output schema, the description says nothing about result shape or volume, which matters for a broad collection search.

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%: the query examples (sunflowers, Egyptian, armor) and the hasImages default of true are fully documented in the schema. The description contributes no additional parameter semantics, so the 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 (search) and resource (the Met's collection of artworks), so an agent knows exactly what it queries. It does not distinguish itself from sibling met_object or met_departments, which an agent would have to resolve by opening schemas.

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?

No indication of when to prefer this over met_object (fetch a specific object) or met_departments, nor any prerequisite or exclusion. The agent is left to infer the search-vs-fetch split from names alone.

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

Deploy Server

Other Tools