Skip to main content
Glama

Fold Laboratories

by com.foldlaboratories
OverviewDiscussionsAdmin

Get artwork detail

get_artwork
Read-onlyIdempotent

Use this when someone wants the full facts about one work before deciding: what it is, its size, how it looks, what delivery costs and when it ships, whether it can be returned, who made it, and what Fold verified about the seller. Full detail for one artwork: attribution, medium, dimensions, edition structure, provenance, seller, and every individual impression that can be bought with its own price and availability. A numbered edition has one entry per impression — including artist proofs (AP), printer proofs (PP), and the bon à tirer (BAT), which are separate objects from the numbered run and usually priced differently. Each entry in attributes says who stands behind it (seller_stated, fold_derived or fold_verified), and a null means unspecified rather than estimated. Also returns image URLs to show the buyer. A signed URL is TEMPORARY: honour its expires_at and re-fetch rather than caching or redistributing it. An image marked permanent is one of the work’s public images, with no expiry: a clean display copy, or, where it also says preview, a reduced copy watermarked by Fold. Use this before presenting a work to a buyer, and quote the impression label exactly as given. Its public images, up to 3, also come as small pictures attached after the answer, so you can see how it looks.

Input Schema

NameRequiredDescriptionDefault
artwork_idYesartwork_id from search_artworks.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior5/5

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

Beyond the read-only/idempotent annotations, it discloses important behavior: signed image URLs are temporary and must not be cached or redistributed; permanent images may be clean or watermarked preview copies; null attribute values mean unspecified rather than estimated; AP/PP/BAT impressions are separate objects and usually priced differently. This is exactly the extra context an agent needs before calling and handling output.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The purpose is front-loaded, but the opening sentence's list of facts is largely repeated by the second sentence ('Full detail for one artwork: attribution, medium, dimensions...'), adding length without new information. The image-URL guidance earns its place, but the overall description could be tightened.

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 no output schema, the description carries the full burden and does so thoroughly: it explains the return structure at a conceptual level, attributes semantics, edition impression handling, image URL expiry rules, and the attached image previews. An agent has enough information to call it and interpret the result correctly.

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?

The schema already documents artwork_id at 100% coverage and even states it comes from search_artworks. The description adds no further syntax, format, or identifier semantics beyond that, so the baseline of 3 is appropriate.

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 uses a specific verb and resource ('full detail for one artwork') and enumerates the returned facets (attribution, medium, dimensions, editions, provenance, seller, images). It is clearly distinguishable from search_artworks by emphasizing single-work depth, and the artwork_id schema reference reinforces the retrieval relationship.

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 gives clear usage context: 'Use this when someone wants the full facts about one work before deciding' and 'Use this before presenting a work to a buyer.' It does not explicitly name alternatives or when-not-to-use cases, but the intended moment is unambiguous.

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

All Fold Laboratories 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