Skip to main content
Glama
Sign In
CAD MCP Server

CAD MCP Server

by 652036
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

get_face_normal

Retrieve the simplified face normal for an axis-aligned CAD face using its solid ID and face ID.

Instructions

Return a simplified face normal for an axis-aligned face 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": {
      "solid_id": "<solid_id>",
      "face_id": "<face_id>"
    },
    "name": "get_face_normal"
  }
}

Input Schema

NameRequiredDescriptionDefault
face_idYes
solid_idYes

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 burden. It implies a read-only operation and hints that the result is snapped/simplified to axis directions, but it never states the return format, whether a normal is returned as a vector or enum, or what happens for non-axis-aligned or curved faces.

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 short sentence with no wasted words, front-loading the action. It is efficient, though the terseness contributes to the under-specification.

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?

There is no output schema, so the description should explain the returned value, but it does not. Combined with 0% parameter coverage and no annotations, an agent lacks enough information to call this tool confidently for anything beyond the most obvious case.

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% for both solid_id and face_id, so the description had room to compensate but does not. It only loosely implies face_id refers to an axis-aligned face; the meaning and accepted format of solid_id are entirely undocumented.

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 description states a clear verb (Return) and resource (simplified face normal), but it does not differentiate itself from nearby siblings like get_face_list, get_topology, or get_entity_properties. The qualifiers 'simplified' and 'axis-aligned' hint at a specific behavior without defining it, leaving the agent to guess what 'simplified' means.

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 indication of when to call this tool versus alternatives such as get_face_list or get_topology, and no prerequisites (e.g., whether the face must be planar or axis-aligned) are given. The agent must infer usage entirely.

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