art-mcp

Get artwork image

get_artwork_image

Fetch an artwork image and caption by source and museum ID to view a work or verify its subject matter. Falls back to museum URL when image is unavailable.

Instructions

Download the image for a single artwork (by source and id) and return it so it can actually be viewed, plus a short caption. Use this whenever the user wants to see a work, or when you need to judge what a work actually depicts rather than trusting its title.

Not every record has an image, and the Art Institute ('artic') serves images from a host behind a bot challenge, so those usually fail with a 403 — prefer another source when you need to display something, and fall back to the museumUrl from search results if an image cannot be fetched.

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": {
      "source": "<source>",
      "id": "<id>"
    },
    "name": "get_artwork_image"
  }
}

Input Schema

Name	Required	Description	Default
`id`	Yes	The provider-native artwork id from search results.
`source`	Yes	The museum source the artwork belongs to.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.2.1Jul 28, 2026

TDQS

A4/5.0

Behavior3/5

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

With no annotations, the description carries full burden. It discloses that not every record has an image and that artic requests usually fail with 403. However, it does not specify the returned image format (e.g., binary, base64) or any size limits. The mention of 'short caption' is vague. More details on what exactly 'return it' means would improve transparency.

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?

The description is front-loaded with the primary use case and includes essential behavioral notes in a second paragraph. It is concise enough, but could be slightly shorter by combining sentences. Overall, every sentence serves a purpose, and the structure is logical.

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?

Given the tool's simplicity (2 params, no output schema), the description covers key aspects: when to use, failure modes, fallback strategy, and return of caption. It does not detail the caption format or the exact image return mechanism, but these are minor omissions. The description is largely complete for an AI agent to decide correctly.

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 is 100% and descriptions exist for both parameters. The description adds extra context: it explains that the 'source' parameter is the museum and that artic has issues, and that 'id' is from search results. This provides real-world semantic value beyond the schema definitions, earning a score above baseline.

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 clearly states the action ('download the image for a single artwork') and the result ('return it so it can actually be viewed, plus a short caption'). It distinguishes from sibling tools by specifying that it retrieves the image data, not just metadata, and mentions fallback behavior. However, it does not explicitly state the return format (e.g., base64 or URL), which could be clearer.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides excellent guidance: 'Use this whenever the user wants to see a work, or when you need to judge what a work actually depicts rather than trusting its title.' It also explicitly warns against using for Art Institute ('artic') due to bot challenges, and suggests preferring other sources and falling back to the museumUrl. This clearly tells when to use the tool and when to avoid it.

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

Deploy Server