Skip to main content
Glama

Clevelandart Get Artwork

clevelandart_get_artwork
Read-onlyIdempotent

Single artwork by accession number (e.g. "1962.158") or numeric id.

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": "1962.158"
    },
    "name": "clevelandart_get_artwork"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYese.g. "1962.158" or "94979"

Output Schema

NameRequiredDescriptionDefault

No arguments

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, so the safety and repeatability profile is fully covered without the description repeating it. The description adds no further behavioral context (e.g. what happens with an unknown or malformed id, or whether accession numbers are normalized), but it also contradicts nothing.

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?

One short sentence with the resource stated first and the accepted identifier formats immediately after; every clause earns its place and there is no redundant wording.

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?

For a single-parameter lookup with full schema coverage, rich annotations and an output schema, the description is essentially complete — the agent knows what it returns (schema) and that it is a safe read (annotations). Only error/fallback behavior for an invalid id is left 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 description coverage is 100% and the single parameter 'id' is already documented with examples identical to those in the description. The description therefore adds no meaning beyond the schema, so the baseline of 3 applies.

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 names the resource ('Single artwork') and the two accepted identifier forms ('accession number (e.g. "1962.158") or numeric id'), so an agent can tell it apart from clevelandart_search as a direct lookup rather than a query. It lacks an explicit verb like 'fetch'/'retrieve', which keeps it just short of a 5.

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 only implied: by framing the input as an accession number or id, it suggests this tool is for when you already have a known identifier, while the sibling clevelandart_search handles discovery. There is no explicit when-to-use/when-not statement or named alternative, so the agent must infer the routing.

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.