Skip to main content
Glama
architectural_modeling_workflow

architectural_modeling_workflow

by Lsc1123

drawing_read_slice

Destructive

Read handoff geometry into a plan or section cut-segment draft, producing slice output that feeds the next drawing workflow step.

Instructions

Read handoff geometry into a plan/section cut-segment draft; final drawing stays in the next workflow.

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": {
      "geometry_path": "<geometry_path>",
      "output_path": "<output_path>",
      "origin_m": "<origin_m>",
      "normal": "<normal>",
      "x_axis": "<x_axis>"
    },
    "name": "drawing_read_slice"
  }
}

Input Schema

NameRequiredDescriptionDefault
idsNo
normalYes
x_axisYes
origin_mYes
output_pathYes
geometry_pathYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.1

TDQS

C2.2/5.0
Behavior2/5

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

Annotations declare readOnlyHint=false and destructiveHint=true, yet the description opens with 'Read', which understates that this writes to output_path and can overwrite existing content. It adds one useful fact ('final drawing stays in the next workflow'), but says nothing about what is created or destroyed at output_path, what permissions are needed, or how ids affect the slice.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

It is a single compact sentence with no filler, which is good, but the brevity comes at the cost of substance rather than from efficiency. The most load-bearing information is packed into an opaque phrase ('cut-segment draft').

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

Completeness2/5

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

For a six-parameter tool with five required parameters and a destructive write annotation, this is far too thin. The existence of an output schema excuses it from describing return values, but it still leaves parameter meaning, write behavior, and prerequisites entirely unaddressed.

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

Parameters1/5

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

All six parameters have 0% schema description coverage and the description explains none of them. geometry_path, output_path, origin_m, normal, x_axis, and ids are all undocumented in both places, leaving the agent to guess formats (units, coordinate frame, path conventions) and the meaning of ids.

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

Purpose3/5

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

The description names a verb ('Read') and a resource ('handoff geometry') and says the result is a 'plan/section cut-segment draft', so the general intent is discernible. However, 'cut-segment draft' is unexplained jargon and nothing distinguishes this from related export/handoff tools in the sibling list, so an agent cannot confidently tell when this is the right entry point.

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 phrase 'final drawing stays in the next workflow' implies this is a preparatory step, but no explicit when-to-use, when-not-to-use, or prerequisite is given. There is no routing guidance relative to handoff_export, sketchup_export, or asset_build, all of which an agent might reasonably consider instead.

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