Skip to main content
Glama

Save a selection mask

save_mask

Stores the user-painted mask area as a Base64 PNG for image editing workflows; intended for internal image-card use rather than direct calls.

Instructions

Used by the image card to store the area the user painted. 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": {
      "data": "<data>"
    },
    "name": "save_mask"
  }
}

Input Schema

NameRequiredDescriptionDefault
dataYesBase64 PNG.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full burden. It discloses caller context but not mutation semantics: whether an existing mask is overwritten, whether the write is reversible, or what a successful call returns. For a write tool with zero annotation coverage, that is a substantial gap.

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, no filler, with the call-context ('used by the image card') front-loaded ahead of the warning. Every sentence earns its place.

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 trivial one-parameter helper with no output schema, the description covers what it stores, who calls it, and the key decision an agent needs (do not invoke directly). Only overwrite and return behavior are left unstated.

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 single parameter has 100% schema description coverage ('Base64 PNG'), and the description adds no format, dimension, or encoding detail beyond that. Baseline 3 applies when the schema already documents all parameters.

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 a specific resource — 'the area the user painted' — which explains what a mask actually is, and the title supplies the verb 'save'. It does not explicitly differentiate from the sibling save_selection, so this is clear purpose without sibling differentiation.

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 tells the agent it is 'not useful to call directly' and that it exists for the image card to call, which is genuine when-not-to-use guidance. It stops short of naming an alternative tool for agents that think they need this capability.

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