Skip to main content
Glama

art

by io.github.pipeworx-io
OverviewDiscussionsAdmin

Search Artworks

search_artworks
Read-onlyIdempotent

Search the Met's collection by subject, artist or keyword (e.g., "sunflowers", "monet", "ancient egypt"). Artworks whose TITLE matches come first, then ones whose ARTIST or culture matches, then general full-text matches; each result says which via matched_on. Returns title, artist, date, medium and image URL.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoHow many artworks to return, 1-20 (default 5).
queryYesSearch query (e.g., "sunflowers", "ancient egypt", "monet")

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
queryYesThe search query used
totalYesTotal matching artworks in collection
showingYesNumber of artworks returned (up to 5)
artworksYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / examples
      Previous value: -[
-  {
-    "query": "sunflowers"
-  },
-  {
-    "query": "Paintings Monet"
-  }
-]New value: +[
+  {
+    "query": "sunflowers"
+  },
+  {
+    "limit": 5,
+    "query": "monet"
+  }
+]
    • addedInput schema / properties / limit
      Added value: +{
+  "description": "How many artworks to return, 1-20 (default 5).",
+  "type": "number"
+}
  2. Changed2 schema fields changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "query": "sunflowers"
+  },
+  {
+    "query": "Paintings Monet"
+  }
+]
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "properties": {
+    "artworks": {
+      "items": {
+        "properties": {
+          "artist": {
+            "description": "Artist display name or 'Unknown'",
+            "type": "string"
+          },
+          "artist_nationality": {
+            "description": "Artist's nationality",
+            "type": "string"
+          },
+          "classification": {
+            "description": "Object classification",
+            "type": "string"
+          },
+          "credit_line": {
+            "description": "Credit and acquisition information",
+            "type": "string"
+          },
+          "date": {
+            "description": "Object date or period",
+            "type": "string"
+          },
+          "department": {
+            "description": "Museum department",
+            "type": "string"
+          },
+          "dimensions": {
+            "description": "Physical dimensions",
+            "type": "string"
+          },
+          "full_image_url": {
+            "description": "Full resolution image URL",
+            "type": "string"
+          },
+          "image_url": {
+            "description": "Small image URL",
+            "type": "string"
+          },
+          "is_public_domain": {
+            "description": "Whether artwork is in public domain",
+            "type": "boolean"
+          },
+          "medium": {
+            "description": "Materials and technique",
+            "type": "string"
+          },
+          "met_url": {
+            "description": "Met Museum URL for artwork",
+            "type": "string"
+          },
+          "object_id": {
+            "description": "Met Museum object ID",
+            "type": "number"
+          },
+          "title": {
+            "description": "Artwork title",
+            "type": "string"
+          }
+        },
+        "required": [
+          "object_id",
+          "title",
+          "artist",
+          "artist_nationality",
+          "date",
+          "medium",
+          "dimensions",
+          "department",
+          "classification",
+          "image_url",
+          "full_image_url",
+          "is_public_domain",
+          "credit_line",
+          "met_url"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "query": {
+      "description": "The search query used",
+      "type": "string"
+    },
+    "showing": {
+      "description": "Number of artworks returned (up to 5)",
+      "type": "number"
+    },
+    "total": {
+      "description": "Total matching artworks in collection",
+      "type": "number"
+    }
+  },
+  "required": [
+    "query",
+    "total",
+    "showing",
+    "artworks"
+  ],
+  "type": "object"
+}
  3. Changed2 schema fields changed
    • removedInput schema / examples
      Removed value: -[
-  {
-    "query": "monet water lilies"
-  },
-  {
-    "limit": 25,
-    "query": "american portrait"
-  }
-]
    • changedOutput schema / (root)
      Previous value: -{
-  "properties": {
-    "artworks": {
-      "items": {
-        "properties": {
-          "artist": {
-            "description": "Artist display name",
-            "type": [
-              "string",
-              "null"
-            ]
-          },
-          "date": {
-            "description": "Date of creation",
-            "type": [
-              "string",
-              "null"
-            ]
-          },
-          "id": {
-            "description": "Artwork ID",
-            "type": "number"
-          },
-          "image_id": {
-            "description": "ARTIC image identifier",
-            "type": [
-              "string",
-              "null"
-            ]
-          },
-          "image_url": {
-            "description": "URL to high-resolution image",
-            "type": [
-              "string",
-              "null"
-            ]
-          },
-          "medium": {
-            "description": "Medium used (e.g., oil on canvas)",
-            "type": [
-              "string",
-              "null"
-            ]
-          },
-          "title": {
-            "description": "Artwork title",
-            "type": "string"
-          }
-        },
-        "required": [
-          "id",
-          "title"
-        ],
-        "type": "object"
-      },
-      "type": "array"
-    },
-    "total": {
-      "description": "Total number of artworks matching the search query",
-      "type": "number"
-    }
-  },
-  "required": [
-    "total",
-    "artworks"
-  ],
-  "type": "object"
-}New value: +null
  4. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "properties": {
+    "artworks": {
+      "items": {
+        "properties": {
+          "artist": {
+            "description": "Artist display name",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "date": {
+            "description": "Date of creation",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "id": {
+            "description": "Artwork ID",
+            "type": "number"
+          },
+          "image_id": {
+            "description": "ARTIC image identifier",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "image_url": {
+            "description": "URL to high-resolution image",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "medium": {
+            "description": "Medium used (e.g., oil on canvas)",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "title": {
+            "description": "Artwork title",
+            "type": "string"
+          }
+        },
+        "required": [
+          "id",
+          "title"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "total": {
+      "description": "Total number of artworks matching the search query",
+      "type": "number"
+    }
+  },
+  "required": [
+    "total",
+    "artworks"
+  ],
+  "type": "object"
+}
  5. Changed1 schema field changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "query": "monet water lilies"
+  },
+  {
+    "limit": 25,
+    "query": "american portrait"
+  }
+]
  6. First observed

TDQS

A4.5/5.0
Behavior5/5

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

Annotations already indicate readOnlyHint=true, idempotentHint=true, and destructiveHint=false, but the description goes well beyond by disclosing the ranking order (title matches first, artist/culture second, full-text last) and that each result includes a matched_on field. It also lists the returned fields, providing rich behavioral detail unavailable from annotations alone.

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 two sentences, front-loaded with purpose and examples, followed by behavior and return fields. Every clause adds value with no redundancy or filler.

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

Completeness5/5

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

With a full output schema (mentioned as present), robust annotations, a simple two-parameter input schema, and the description adding ranking and matched_on behavior, the tool is fully specified. The agent can correctly select and invoke this tool without additional elaboration.

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 100%, with query and limit fully documented. The description adds examples and explains how the query is interpreted (subject, artist, or keyword), but this largely mirrors the schema. It does not significantly enhance parameter understanding beyond what is already in the structured fields.

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 what the tool does: 'Search the Met's collection by subject, artist or keyword' with concrete examples. It distinguishes the tool from siblings by focusing on collection search and including ranking logic, which differentiates it from get_artwork, get_departments, and search_within.

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?

The description gives clear context for when to use the tool ('Search the Met's collection') and provides example queries. However, it does not explicitly mention alternatives or when not to use, such as pointing to get_artwork for specific artwork retrieval, so it lacks explicit exclusion guidance.

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

All art toolsInspect
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.

Resources