Skip to main content
Glama

flip

Mirrors an ASCII/braille canvas horizontally or vertically, swapping mirror-able drawing glyphs so line art stays coherent while letters remain unchanged.

Instructions

Mirror the canvas. 'horizontal' flips left-right, 'vertical' flips top-bottom. Mirror-able drawing glyphs (slashes, brackets, box corners) are swapped so line art stays coherent; letters are left as-is. Great for building symmetry.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "flip"
  }
}

Input Schema

NameRequiredDescriptionDefault
axisNo'horizontal' = left-right mirror, 'vertical' = top-bottom mirror.horizontal

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A3.5/5.0
Behavior3/5

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

With no annotations, the description carries the full disclosure burden, and it does add real behavior beyond the schema: mirror-able glyphs (slashes, brackets, box corners) are swapped while letters are preserved, so line art stays coherent. However, it never says whether the flip is applied in place or returns a new canvas, whether it is reversible/undoable, or what happens to existing canvas state — meaningful gaps for a mutating canvas operation.

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?

Three short sentences, front-loaded with the core action, then axis semantics, then glyph rules, then a use case. No filler; only the trailing 'Great for building symmetry' is arguably soft, but it earns its place as a use hint.

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 one-optional-parameter tool with an enum-constrained axis and no output schema, the description covers the transformation semantics and the non-obvious glyph-swapping rule well. The residual gap is state/mutation semantics (in-place vs returned result, undo), which matters but is modest given the tool's simplicity.

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 enum already documents 'horizontal' = left-right and 'vertical' = top-bottom. The description restates that mapping with essentially the same wording, adding no additional meaning; baseline 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?

'Mirror the canvas' states a specific verb (mirror) and resource (canvas), which is clearly distinct from siblings like crop, resize_canvas, or erase. It doesn't explicitly name a contrasting sibling, but the operation is unambiguous enough that an agent can select it without opening the schema.

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?

The closing line 'Great for building symmetry' implies when the tool is useful, but there is no explicit when-to-use/when-not guidance and no named alternative (e.g., versus redrawing with draw_* tools). Usage is inferable, not stated.

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