Skip to main content
Glama

Artic Get Artwork

artic_get_artwork
Read-onlyIdempotent

Get complete details for an artwork by ID. Returns title, artist, date, medium, dimensions, description, credit line, and high-resolution image.

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "id": 27992
    },
    "name": "artic_get_artwork"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesARTIC artwork ID (e.g., 27992)

Output Schema

NameRequiredDescriptionDefault
idYesArtwork ID
dateNoDate of creation
titleYesArtwork title
artistNoArtist display name
mediumNoMedium used (e.g., oil on canvas)
image_idNoARTIC image identifier
image_urlNoURL to high-resolution image
dimensionsNoPhysical dimensions of artwork
credit_lineNoCredit line or acquisition information
descriptionNoDetailed artwork description

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=true, so the safety and idempotency profile is fully covered without the description. The description adds the returned field list, which is mild behavioral context but largely duplicates the output schema; it says nothing about behavior when an ID is invalid or not found, or about rate limits.

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 short sentences, zero filler, and the core action is front-loaded in the first clause. Every sentence earns its place.

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?

This is a simple single-parameter lookup with a full output schema and complete annotations, so the description does not need to explain return values or safety. The only real gap is what happens on an unknown or invalid ID, which matters for an agent deciding whether to retry.

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?

There is a single parameter with 100% schema description coverage ("ARTIC artwork ID (e.g., 27992)"), so the schema already carries the full semantic load including an example value. The description adds only the phrase "by ID" and no format, range, or sourcing guidance beyond it.

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?

"Get complete details for an artwork by ID" names a specific verb (get), a specific resource (artwork), and the lookup key (ID), which implicitly separates it from artic_search_artworks and artic_get_artist. It stops short of explicitly naming those siblings, so differentiation is inferred rather than stated.

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

Usage Guidelines3/5

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

Usage is implied by "by ID" — an agent can reason that this is the follow-up call once an ID is known from a search. However, there is no explicit when-to-use, when-not-to-use, or named alternative, so the agent must infer the search-then-fetch workflow itself.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.