Skip to main content
Glama
Sign In
CAD MCP Server

CAD MCP Server

by 652036
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

set_view_standard

Stores the active drawing standard for a named view in parameter state so later CAD operations reference the chosen standard.

Instructions

Store active drawing standard in parameter state.

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": {
      "view_name": "<view_name>"
    },
    "name": "set_view_standard"
  }
}

Input Schema

NameRequiredDescriptionDefault
view_nameYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.4/5.0
Behavior2/5

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

With no annotations, the description carries the full behavioral burden and states only that something is 'stored.' It does not say whether this mutates an existing view, whether it persists across sessions, whether it can be undone, or whether view_name must reference an existing view.

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?

A single short sentence with no waste, but its brevity stems from under-specification rather than efficiency; there is no front-loaded rationale for the tool's role.

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 state-mutating tool with no annotations, no output schema, and an undocumented required parameter, the description should explain the affected object and persistence behavior. It leaves all of that to inference.

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

Parameters2/5

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

Schema coverage is 0% for the single parameter, and the description never explains what view_name accepts (an existing view name? a new one?) or what a 'standard' value is. The only hint is the word 'view' echoed in the tool name, which is insufficient compensation.

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 verb 'Store' and the resource 'active drawing standard' are identifiable, but the phrase 'in parameter state' is jargon that never explains what a view standard is or how it relates to the view_name input. It is not distinguishable from siblings like set_parameter or set_drawing_scale without guessing.

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?

No indication of when to call this versus set_parameter/update_parameter/set_drawing_scale, no prerequisites, and no mention of when the stored standard takes effect. The agent gets no routing guidance at all.

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