Skip to main content
Glama

sch_place_text_frame

Place a bordered, word-wrapping text frame (note block) on the active schematic sheet by specifying two corner coordinates in mils and optional alignment.

Instructions

Place a multi-line text frame (note block) on the active sheet.

A text frame is a bordered rectangle that word-wraps a block of text. Use \n in text for explicit line breaks.

Args: x1, y1, x2, y2: The two rectangle corners in mils. text: Frame contents (use \n for line breaks). align: Horizontal alignment "left", "center", or "right".

Returns: Dict confirming placement and the frame corners.

Input Schema

NameRequiredDescriptionDefault
x1Yes
x2Yes
y1Yes
y2Yes
textYes
alignNoleft

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.6.1

TDQS

A3.9/5.0
Behavior3/5

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

No annotations are present, so the description carries the full behavioral burden. It states that the tool places text on the active sheet and returns a confirmation dict, but it does not discuss permissions, reversibility, interaction with existing frames, or other side effects of this mutation.

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?

The description is front-loaded with the core action, then uses compact Args and Returns sections with no filler. Every sentence contributes useful information.

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?

The tool has six parameters, no annotations, and a 0% schema description coverage; the description fills the parameter documentation gap and even explains the return value. It is complete enough for correct invocation, though it still lacks guidance on selecting this tool over sibling placement tools.

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

Parameters5/5

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

Schema description coverage is 0%, yet the description documents every parameter: x1/y1/x2/y2 as rectangle corners in mils, text as frame contents with explicit line-break support, and align with valid values 'left', 'center', and 'right'. This fully compensates for the missing schema descriptions.

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 gives a specific verb and resource: 'Place a multi-line text frame (note block) on the active sheet.' It also explains what a text frame is, which helps distinguish it from a generic rectangle, but it does not explicitly differentiate it from the sibling sch_place_note.

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 description implies usage by defining the text frame as a bordered, word-wrapping note block, but it never states when to use this tool instead of sch_place_note, sch_place_rectangle, or other placement siblings. No explicit alternatives or exclusions are provided.

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

Deploy Server

Other Tools