Skip to main content
Glama

Balloon Drawing

balloon_drawing
Destructive

Assign persistent inspection balloon numbers to dimensions and feature notes on a drawing page, exporting them to SVG/PDF for inspection plans and FAI reports.

Instructions

Number every characteristic on a drawing page (dimensions, feature control frames, feature notes) with an inspection balloon, rendered on SVG/PDF export; inspection_plan and fai_report key their rows on it.

Numbers are a persistent IDENTITY: re-running reassigns nothing, a new dimension gets the next number, a deleted one RETIRES its number (never reused). renumber=True restarts from 1 and invalidates existing inspection records. Call after dimensions are placed and fit_page has run.

Returns {count, balloons (source object name -> number), assigned, kept, retired, next_balloon}.

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": {
      "page": "<page>"
    },
    "name": "balloon_drawing"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageYes
renumberNo
workspaceNoRun this call in this named workspace

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.5.7
    • addedInput schema / properties / workspace
      Added value: +{
      +  "default": "",
      +  "description": "Run this call in this named workspace",
      +  "title": "Workspace",
      +  "type": "string"
      +}
  2. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Annotations already flag destructiveHint=true and non-readOnly, and the description earns that by specifying exactly what is destructive: renumber=True restarts numbering and invalidates existing inspection records. It further discloses non-obvious identity semantics (no reassignment on re-run, retirements never reused) that no annotation could convey.

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?

Front-loaded with the core action, zero filler, and the arrow/brace notation packs return keys tightly. The middle section is dense enough that an agent must parse two long parenthetical sentences, which costs a little readability, but nothing is redundant.

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

Completeness5/5

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

No output schema exists, and the description compensates by enumerating the return fields, including the balloons mapping. Combined with the destructive-renumber warning, ordering prerequisite, and downstream consumer note, an agent has everything needed to invoke it safely.

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?

With only 33% schema description coverage, the description carries real weight and does: it defines renumber's semantics and blast radius precisely, and 'page' is contextualized as a drawing page. 'workspace' semantics remain entirely to the schema, and no format examples for page are given, so not a full 5.

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?

Specific verb and resource: numbers every characteristic on a drawing page with inspection balloons, naming exactly what gets ballooned (dimensions, feature control frames, feature notes) and what consumes the numbers downstream (inspection_plan, fai_report). This is unmistakably distinct from siblings like add_dimension, add_gdt_callout, or inspection_plan.

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?

Gives a clear sequencing precondition ('call after dimensions are placed and fit_page has run') and a conditional branch for renumber=True, which is effectively a when-to-use rule with a stated consequence. It stops short of naming an alternative tool to use instead when balloons already exist, so a 4 rather than a 5.

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