Skip to main content
Glama

View a saved MCPaint image

get_saved_image
Read-onlyIdempotent

Retrieve a drawing saved by MCPaint using the imageId supplied by the app or user. Returns a normal MCP image content block so you can see the image even when app-to-chat image messages are unsupported. Saved images expire after 24 hours. The client must support images in tool results. Do not invent or guess image IDs.

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": {
      "imageId": "<imageId>"
    },
    "name": "get_saved_image"
  }
}

Input Schema

NameRequiredDescriptionDefault
imageIdYesThe imageId from a saved MCPaint reference.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior5/5

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

Beyond the readOnly/idempotent/destructive annotations, the description discloses the return format (a normal MCP image content block), a critical non-obvious constraint (saved images expire after 24 hours), and a client capability requirement (tool results must support images). These are exactly the behavioral facts annotations cannot carry.

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?

Four short sentences, front-loaded with purpose and return behavior, each carrying information. The final 'do not invent' sentence partially overlaps the schema's 64-hex-character pattern, a small redundancy, but nothing is padded.

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?

For a single-parameter read tool with no output schema, the description supplies everything an agent needs: what is returned, how long it remains valid, what the client must support, and a warning against fabricated identifiers. No material gaps remain.

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?

With one parameter and 100% schema description coverage, including a regex pattern, the schema already fully specifies imageId. The description adds only a light constraint ('do not invent or guess image IDs') and the ID's source, which is marginally more than the structured data provides.

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 gives a specific verb and resource: 'Retrieve a drawing saved by MCPaint', and adds scope detail (using the imageId from the app or user). It does not name or contrast with the sibling open_paint, so an agent gets no explicit differentiation, but the function itself is unambiguous.

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 rather than stated: it tells the agent where the imageId comes from and forbids inventing IDs, which is genuine when-to-use guidance. It never says when not to call it or what to do instead (e.g., use open_paint to create a new drawing), so alternatives remain implicit.

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