Skip to main content
Glama
Sign In
CAD MCP Server

CAD MCP Server

by 652036
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

get_entity_properties

Retrieve a single entity record by its ID to inspect CAD properties and support precise drawing edits.

Instructions

Return one entity record by id.

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_id": "<entity_id>"
    },
    "name": "get_entity_properties"
  }
}

Input Schema

NameRequiredDescriptionDefault
entity_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.8/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full behavioral burden. 'Return' implies a read operation, but it does not state what happens when the id is missing, whether permissions are required, or any other behavioral detail beyond the bare operation.

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

Conciseness5/5

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

The description is a single, front-loaded sentence with no wasted words. Its brevity is appropriate for a simple getter, even though it leaves other dimensions under-specified.

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 has no annotations and no output schema, so the description should provide more context about return records, errors, or id sourcing. It is too sparse to fully prepare an agent to invoke the tool correctly in the broader CAD/project sibling set.

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%, and the only parameter is entity_id. The description adds only 'by id,' which restates the parameter name without giving format, source, or validity constraints. It does not compensate for the missing schema-level documentation.

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 clear verb-resource pair: return one entity record identified by id. It is distinguishable from broad list/search siblings, but it does not explicitly contrast with close alternatives such as list_entities, get_entity_type, or find_entities_by_property.

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 siblings. The agent can infer it is a single-entity lookup, but the description provides no context, prerequisites, or alternative-selection criteria.

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