Skip to main content
Glama
AutoCAD MCP

AutoCAD MCP

set_profile

Add or correct a profile catalog entry with article, name, role, depth, and inertia values for structural calculations.

Instructions

Добавить или исправить профиль в каталоге: article, name, role (стойка, ригель, стропило, рама, импост, створка, прижим, крышка, прочее), depth_mm, ix_cm4 (момент инерции для статрасчёта, по каталогу системодателя).

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": {
      "article": "<article>"
    },
    "name": "set_profile"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNo
roleNoпрочее
ix_cm4No
articleYes
depth_mmNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.0

TDQS

A3.8/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full burden; it does disclose the important mutation semantics (add-or-correct, i.e. upsert against a catalog). It does not say whether correcting overwrites unspecified fields, what identifies the record (presumably article), or what permissions/validation apply.

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?

A single dense sentence that front-loads the action and then enumerates the fields. Every clause carries information; only the trailing supplier-catalog note is arguably expendable.

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?

With an output schema present, return values need no explanation, and the description fully covers the five inputs plus the create-or-update nature of the call. Remaining gaps are modest: units for depth_mm and how an existing profile is matched/merged on correction.

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 coverage is 0%, yet the description names all five parameters and adds meaning the schema lacks: the role value vocabulary (стойка, ригель, стропило, рама, импост, створка, прижим, крышка, прочее) and the purpose of ix_cm4 (moment of inertia for structural calculation, taken from the supplier catalog). This more than compensates for the empty 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?

States a specific verb pair and resource: add or correct a profile in the catalog. It is instantly distinguishable from the drawing/annotation siblings, though it never explicitly contrasts itself with any named alternative.

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?

'Добавить или исправить' implies an upsert pattern, so an agent can infer this is the call for creating or amending a catalog profile. There is no explicit when-to-use/when-not guidance, no prerequisites, and no mention of which sibling handles reading or deleting profiles.

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