Skip to main content
Glama
Sign In
CAD MCP Server

CAD MCP Server

by 652036
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

create_group

Combine multiple CAD entity IDs into a named group to organize and manage drawing objects.

Instructions

Create a named group from entity ids.

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": {
      "entity_ids": "<entity_ids>"
    },
    "name": "create_group"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNo
entity_idsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.7/5.0
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states a create action but does not mention permissions, side effects, error conditions, or what happens to existing entities, leaving important behavioral traits unspecified.

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 single sentence is front-loaded and contains no wasted words. However, it is arguably too terse for a tool with multiple parameters and no other documentation.

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?

The tool is a mutation operation with no output schema, no annotations, and 0% schema description coverage. The description does not explain return behavior, required permissions, or parameter constraints, leaving it incomplete for an agent to invoke correctly.

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 description coverage is 0%, so the description should compensate but does not. It merely restates the property concepts ('named' for name, 'entity ids' for entity_ids) without adding format, constraints, or meaning beyond what the schema property names already imply.

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: create a named group from entity ids. It clearly distinguishes the action from siblings like ungroup or select_group, though it does not explicitly name alternatives.

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?

There is no guidance on when to use this tool versus alternatives such as create_assembly or select_group. The only implied usage is grouping entities, which is not elaborated.

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