Skip to main content
Glama

set_frame

Enable or disable a decorative map frame and optionally set its texture and size when preparing a Wonderdraft map for export or preview.

Instructions

Turn the decorative map frame on/off; texture and size are optional. texture is one of Wonderdraft's frames: celtic_dotted, celtic_leaves, celtic_woven_1, celtic_woven_2, checkered_opaque, checkered_transparent, double_pen_opaque, double_pen_transparent, double_pen_vignette, entwined_corner_opaque, entwined_corner_transparent, hatch_opaque, hatch_transparent, old_ink_opaque, old_ink_transparent, solid_line_opaque, solid_line_tansparent (sic).

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": {
      "enabled": "<enabled>"
    },
    "name": "set_frame"
  }
}

Input Schema

NameRequiredDescriptionDefault
sizeNo
enabledYes
textureNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.3/5.0
Behavior3/5

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

With no annotations supplied, the description carries the full behavioral burden, and it does convey the core effect: toggling a decorative frame on the map. However, it does not say what happens to a previously set texture when enabled=false, whether texture/size are ignored or retained on disable, whether size is in pixels or map units, or whether the frame affects rendering or export. Those are material gaps for a state-mutating toggle with zero annotation coverage.

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?

The purpose is front-loaded in the first clause, followed by optionality and then the value list, which is a sensible order. The long texture enumeration earns its space because the schema has no enum, though the '(sic)' typo on 'solid_line_tansparent' adds noise and risks a bad value being passed.

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 three-parameter mutation tool with no annotations and no output schema, the description covers the toggle and the texture vocabulary adequately but leaves the size parameter and post-call state (what the map looks like, whether prior settings persist) unexplained. It is workable but not complete enough to call without guessing on at least one parameter.

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

Parameters4/5

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

Schema description coverage is 0%, so the description must supply parameter meaning, and it does the most valuable part: it enumerates all 18 valid texture identifiers and explains they are Wonderdraft frame names, which the schema does not. It also flags texture and size as optional. The gap is size, whose units and valid range remain undefined anywhere.

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 opens with a specific verb and resource: 'Turn the decorative map frame on/off.' That is unambiguous and clearly distinct from sibling tools like add_label, add_symbol, or apply_theme, none of which manipulate the map frame. It does not explicitly contrast itself with any named alternative, which keeps it just short of a 5.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The only usage signal is that 'texture and size are optional', which tells the agent about defaults but not about when to reach for this tool versus other map-decoration tools. There is no statement of prerequisites, side effects on existing frames, or conditions under which texture/size should be supplied. An agent must infer everything about context from the one-line purpose.

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