Skip to main content
Glama
AutoCAD MCP

AutoCAD MCP

static_calc

Calculates deflection and checks structural profiles for mullions, posts, or rafters under snow and wind loads, then can generate an A4 calculation sheet in AutoCAD.

Instructions

СТАТИЧЕСКИЙ РАСЧЁТ стойки, импоста или стропила на прогиб (СНиП 2.01.07-85*, табл. 42 СНиП 2.03.06-85), как в проектах. length_mm: длина элемента между опорами, angle_deg: угол к горизонтали (90 = вертикальная стойка), step_mm: шаг стоек, glass_mm: общая толщина стекла в стеклопакете, snow_region I..VIII, wind_region Iа..VII, terrain A/B/C, height_m: высота объекта, igu: стеклопакет (прогиб L/300) или одинарное стекло (L/200), steel: сталь вместо алюминия. Профиль подбирается из каталога (list_profiles) или задаётся article. draw=True: лист расчёта А4 в чертеже.

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": {
      "length_mm": "<length_mm>",
      "angle_deg": "<angle_deg>",
      "step_mm": "<step_mm>"
    },
    "name": "static_calc"
  }
}

Input Schema

NameRequiredDescriptionDefault
xNo
yNo
iguNo
drawNo
sheetNo
steelNo
numberNo
sheetsNo
articleNo
step_mmYes
terrainNoB
glass_mmNo
height_mNo
angle_degYes
developerNo
length_mmYes
object_nameNo
snow_regionNoII
wind_regionNoII

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.0

TDQS

A4.4/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does significant work: it cites the governing norms (SNiP 2.01.07-85*, table 42 of SNiP 2.03.06-85), discloses the deflection limit selection (L/300 for IGU vs L/200 for single glazing), and states that steel can replace aluminum. It does not say what the calculation returns or whether it writes to a drawing, though an output schema exists to cover return values.

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 a capitalized label followed by the normative references, then parameter meanings in a compact run-on list. It is dense but each clause adds information; the one weakness is that the single paragraph blurs parameter documentation into the purpose statement, which slightly hurts scanability.

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?

For a 19-parameter engineering calculation tool with an output schema, the description covers the purpose, the normative basis, the profile-source path, and most domain parameters. It leaves out what the calculation actually emits beyond the A4 sheet and how failures or invalid profiles are reported, which keeps it shy of a 5.

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% on 19 parameters, so the description must compensate, and it does: it documents length_mm, angle_deg (with 90 = vertical post), step_mm, glass_mm, snow_region (I..VIII), wind_region (Iа..VII), terrain (A/B/C), height_m, igu, steel, article, and draw with meaning and, where relevant, allowed ranges. The remaining undocumented parameters (x, y, sheet, sheets, number, object_name, developer) are self-evident metadata, so the substantive gaps are closed.

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?

The description opens with a specific verb+resource in caps: static calculation of a post, impost, or rafter for deflection per SNiP norms. It names the exact reference tables and distinguishes the tool from the catalog lookup (list_profiles) by pointing to the profile-selection path. An agent can tell this apart from any sibling.

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?

It states that the profile comes either from the catalog (list_profiles) or via the article parameter, which routes the agent to the sibling tool when a profile is needed, and it explains that draw=True produces an A4 calculation sheet. It does not give explicit when-not-to-use or exclusion criteria, so it falls short of 5.

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