Skip to main content
Glama

art

by io.github.pipeworx-io

Get Artwork

get_artwork
Read-onlyIdempotent

Get full details for a specific artwork. Provide the object ID from search results. Returns title, artist, date, medium, department, and high-resolution image URL.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
object_idYesMet Museum object ID (e.g., 436535)

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
dateYesObject date or period
titleYesArtwork title
artistYesArtist display name or 'Unknown'
mediumYesMaterials and technique
met_urlYesMet Museum URL for artwork
image_urlYesSmall image URL
object_idYesMet Museum object ID
departmentYesMuseum department
dimensionsYesPhysical dimensions
credit_lineYesCredit and acquisition information
classificationYesObject classification
full_image_urlYesFull resolution image URL
is_public_domainYesWhether artwork is in public domain
artist_nationalityYesArtist's nationality

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and idempotentHint, covering the safety profile. The description adds value by listing the returned fields (title, artist, etc.) and image URL, giving insight into the output.

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 concise sentences with the purpose front-loaded and no filler. Every sentence contributes essential information.

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 one parameter, comprehensive annotations, an output schema, and a description covering return fields, the tool is complete for its simple read-only purpose.

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?

The schema already documents object_id with an example. The description supplements it by noting the ID comes from search results, providing additional context 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?

The description clearly states the tool retrieves full details for a specific artwork, distinguishing it from search_artworks which lists results. The phrase 'from search results' positions it as a follow-up to search.

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?

It explicitly instructs to provide the object ID from search results, implying use after search_artworks. No exclusions are given, but the context is clear enough for correct tool selection.

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
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

Tools are a mix of art-related and Pipeworx data tools, with no clear boundary. Many Pipeworx tools overlap in functionality (e.g., ask_pipeworx, deep_research, bet_research), causing confusion. Art tools are distinct but sparse.

Naming Consistency2/5

Tool names mostly use snake_case but follow inconsistent patterns: some are verb-based (ask_pipeworx, search_artworks), others are noun-based (entity_profile, pipeworx_feedback). There is no unified convention across the server.

Tool Count1/5

33 tools is excessive for an art-focused server; only 4 tools (search_artworks, get_artwork, get_departments, generate_llms_txt) relate to art. The rest are from a different domain (Pipeworx), creating a severe scope mismatch.

Completeness2/5

For the art domain, only basic search and retrieval are provided; missing browsing, filtering, or creation tools. The Pipeworx tools are comprehensive but irrelevant to the server's stated purpose, leaving the art surface incomplete.

Resources