Skip to main content
Glama

Get one artwork

get_art
Read-only

Details of one piece by catalogue id, entry number or title: description, caption, good-for line, formats unlocked by purchase, free 256px preview (optionally returned as an image), buy URL and licence. Free.

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

Input Schema

NameRequiredDescriptionDefault
idYesCatalogue id (e.g. 2026-09-13-charge-remembers), entry number (e.g. 1) or title.
include_preview_imageNoAlso return the free 256px preview as an image.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety is covered; the description adds genuinely new behavior: access is "Free", a 256px preview is free, purchased formats are the paywalled part, and the preview can optionally be returned as an image. It does not say what happens for an unknown id, which keeps it off a 5.

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?

A single front-loaded sentence: identity and lookup key first, returned fields after, with the free/preview caveat trailing. No filler and nothing that could be cut without losing information.

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?

With no output schema, the description carries the return-value burden and does so by naming each field plus the optional image variant. For a simple two-parameter read tool this is close to complete; only ambiguous-match or not-found behavior is unaddressed.

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%, and the schema already documents the three accepted id forms and the include_preview_image default. The description restates the id forms without adding format or resolution rules (e.g. precedence when a title matches multiple works). Baseline 3 is appropriate when the schema does the lifting.

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?

States a specific verb and resource ("Details of one piece") and enumerates exactly what comes back: description, caption, good-for line, unlocked formats, preview, buy URL and licence. The singular "one piece" contrasts implicitly but clearly with the plural sibling list_art, so an agent can distinguish them.

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 the required id lookup ("by catalogue id, entry number or title") rather than stated. There is no explicit pointer to list_art or suggest_art for discovery, nor a when-not condition. The reader must infer that this is the detail-fetch step after an id is known.

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.

Resources