Skip to main content
Glama

save_to_gallery

Publish the current ASCII/braille drawing to the public home page or save it to a local gallery folder by providing a title.

Instructions

Publish the current drawing. With the public backend configured it appears on the site's home page; otherwise it is saved to a local gallery folder.

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": {
      "title": "<title>"
    },
    "name": "save_to_gallery"
  }
}

Input Schema

NameRequiredDescriptionDefault
titleYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

B3/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 usefully discloses the backend-dependent outcome (home page vs local folder), but says nothing about whether publishing is idempotent, what happens if a drawing with the same title already exists, whether it requires configuration/credentials, or whether the local save overwrites anything.

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?

Two compact sentences, front-loaded with the action and followed by the outcome variants. No filler; only marginal gain would come from naming the title parameter.

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

Completeness3/5

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

For a single-parameter action with no annotations and no output schema, the description covers the destination logic but leaves the agent guessing about return values (URL, path, or ID), title semantics, and repeat-publish behavior — meaningful gaps for an action whose whole purpose is producing an artifact.

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?

There is one required parameter, 'title', with 0% schema description coverage, and the description never mentions it. The minLength/maxLength constraints are in the schema, but nothing explains what the title is used for (artifact name? home-page label?) or whether it must be unique.

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 verb and object: publish the 'current drawing', and clarifies the two possible destinations. An agent can tell this is the terminal save/publish action, distinct from the drawing/rendering siblings, though it never names or rules out any sibling explicitly.

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 — the phrase 'current drawing' signals it must be called after canvas manipulation, but there is no explicit when-to-use/when-not guidance, no note on whether it should be called once or repeatedly, and no mention of prerequisites.

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