Skip to main content
Glama

Remember what is open in the image card

save_selection

Captures the active image and painted mask or selected regions from the image card, letting Tintloom target edits to the user's current selection.

Instructions

Used by the image card to say which image the user has open and what they painted on it. Not useful to call directly.

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": {
      "image": "<image>"
    },
    "name": "save_selection"
  }
}

Input Schema

NameRequiredDescriptionDefault
maskNoBase64 PNG.
eraseNo
imageYes
regionsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/5.0
Behavior3/5

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

No annotations, so the description carries the burden. It discloses that this is a UI-driven state save rather than a direct-call tool, but it says nothing about persistence semantics, whether it overwrites prior selection, or the size cost of a base64 mask payload.

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, the purpose first and the caveat second. No wasted wording.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no annotations, no output schema, and three of four parameters undescribed in the schema, the description would need to explain mask, erase, and regions. It does not, so an agent only knows to avoid calling it, not what calling it would do.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is only 25%, so the description must compensate and mostly does not. 'What they painted on it' vaguely gestures at mask/erase/regions, but the meaning of erase, the expected regions object shape, and mask size constraints are left undocumented.

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?

States a specific act: recording which image the user has open and what was painted on it, tied to the image card. It is clear enough to distinguish from save_mask or save_layer_arrangement, though it never names the resource it persists as.

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?

Explicitly says 'Not useful to call directly,' which is a genuine exclusion that steers an agent away from invoking it. It does not name which sibling should be used instead, so the guidance is strong but not complete.

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