Skip to main content
Glama

Drawing Legibility

drawing_legibility
Read-only

Flags overlapping dimension labels, dimension lines crossing views, and graphics outside the sheet border to verify drawing legibility.

Instructions

Legibility gate for a drawing page: on the ACTUAL placed graphics, flag the ways the layout becomes unreadable — overlapping dimension labels, a dimension line crossing a view it does not reference, or anything past the sheet border.

min_gap (mm) is the breathing room required between two labels. Returns {ok, violations, labels, segments, views}; each violation has a code (overlap/crosses_view/out_of_border) and a human reason. ok=True means the placed dimensions read cleanly on the sheet. Inspection balloons count as placed graphics too — a numbered circle sitting on a neighbour or off the sheet is flagged like any other label.

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

Input Schema

NameRequiredDescriptionDefault
pageYes
min_gapNo
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/5.0
Behavior5/5

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

The description adds substantial behavioral context beyond the annotations: it explains what is checked, what ok=True means, the violation code taxonomy, human-readable reasons, and that inspection balloons are treated as placed graphics. It also discloses the return structure even though no output schema exists.

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 tool's purpose and then efficiently layers in parameter meaning, return structure, ok semantics, and a useful scope clarification about balloons. Every sentence contributes information needed to invoke or interpret the tool.

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?

Given the lack of an output schema, the description does a good job explaining the return shape and violation semantics. It is nearly complete, with only minor gaps around the exact page parameter identity and any preconditions for the drawing page.

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?

The description meaningfully explains min_gap as the required breathing room between labels and gives its unit (mm). However, with only 33% schema description coverage, it does not clarify the page parameter's expected form (name, id, index) and leaves workspace semantics mostly to the schema.

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 states a specific verb and resource: it flags unreadable layout conditions on a drawing page using actual placed graphics. The exact violation categories (overlap, crosses_view, out_of_border) make the purpose clear, though it does not explicitly differentiate itself from sibling tools such as drawing_gate.

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?

Usage is implied by the phrase 'Legibility gate for a drawing page' and by the focus on placed graphics, suggesting it should be run after dimensions and annotations are placed. However, there is no explicit when-to-use guidance, no exclusions, and no named alternative such as drawing_gate.

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