Skip to main content
Glama
Sign In
CAD to Print MCP

CAD to Print MCP

by Kayrim
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

inspect_freecad_document

List solid objects, dimensions, and validity from a FreeCAD .FCStd document to verify parts before export or slicing.

Instructions

List solid objects, dimensions and validity from a FreeCAD .FCStd document.

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": {
      "path": "<path>"
    },
    "name": "inspect_freecad_document"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/5.0
Behavior3/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. 'List' implies read-only inspection and it names returned data, but it does not state that the document is not modified, error behavior, or file access requirements. This is minimal but adequate for an inspect 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?

A single front-loaded sentence with no wasted words. It delivers the tool's purpose and scope immediately.

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?

An output schema exists, so return values need not be explained in the description. The description covers what is listed and the file type to inspect; only path parameter semantics and explicit read-only confirmation are missing for this low-complexity tool.

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 required path parameter, and the schema only labels it 'Path' with no description. The description adds that the path refers to a FreeCAD .FCStd document but does not specify path format, extension expectations, or whether it must be absolute.

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 ('List') and resources ('solid objects, dimensions and validity') scoped to a FreeCAD .FCStd document. It is easy to distinguish from export_freecad_stl by the inspection verb, but it never references or differentiates from any sibling explicitly.

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?

No explicit when/when-not guidance or alternatives are given. The intended use case (inspect a FreeCAD document) is implied by the verb and resource, so there is minimal but inferable guidance.

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