Skip to main content
Glama

frame

Wrap an ASCII/braille canvas in a box-drawing border with optional centered title and padding; trim first to make a border that hugs the artwork for gallery cards.

Instructions

Wrap the whole canvas in a box-drawing border, growing it by one cell (plus padding) on each side. An optional title sits centered on the top edge. Trim first for a border that hugs the art — great for a gallery card.

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": "frame"
  }
}

Input Schema

NameRequiredDescriptionDefault
styleNoBorder look: 'unicode' (┌─┐), 'round' (╭─╮), 'double' (╔═╗), 'bold' (┏━┓), or 'ascii' (+-+).unicode
titleNoOptional caption centered on the top edge.
paddingNoBlank cells between the art and the border.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A4/5.0
Behavior3/5

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

With no annotations, the description does disclose real behavior: the canvas grows by one cell per side and the title is centered on the top edge. It does not say whether the operation mutates the existing canvas in place or returns a new one, nor how it behaves at size limits — meaningful gaps for a canvas-mutating tool.

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?

Three short sentences, front-loaded with the core action and growth semantics, then the optional title, then the workflow tip. Nothing is redundant or padded.

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 simple three-optional-parameter tool with no output schema, the description covers effect, sizing, and the trim workflow. The only missing piece is mutation semantics (in-place vs. returned canvas), which is a modest gap rather than a blocking one.

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 coverage is 100%, so the enum styles, title, and padding bounds are already fully documented. The description reinforces padding and title placement but adds no format or constraint detail beyond the schema, so baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource — wrap the whole canvas in a box-drawing border — and immediately quantifies the effect (grows one cell per side plus padding). This is clearly distinguishable from siblings like trim, crop, and resize_canvas.

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 names the alternative and the sequencing: 'Trim first for a border that hugs the art' plus a motivating use case (gallery card). Clear context, though it gives no explicit when-not-to-use guidance or note about borders on an empty canvas.

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