Skip to main content
Glama
freecad-mcp-headless

freecad-mcp-headless

by pitbuild

parameters

Lists all parametric expressions and spreadsheet aliases in a FreeCAD document, helping you audit or debug model dependencies without a GUI.

Instructions

List every parametric expression and spreadsheet alias in the document.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "parameters"
  }
}

Input Schema

NameRequiredDescriptionDefault
documentNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.6/5.0
Behavior2/5

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

With no annotations supplied, the description carries the full behavioral burden, yet it only implies read-only through the verb "List". It says nothing about whether it reads the active document or a named one, whether aliases and expressions may be empty, or what a caller should do with the results.

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?

One short sentence with the resource named up front and no filler. It is efficient, though its brevity is partly the cause of the missing semantics rather than purely a virtue.

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 is the only place a caller could learn the shape of the returned list of expressions and aliases, and it omits that entirely. For a simple read tool this is a notable but not fatal gap.

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

Parameters1/5

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

The single optional parameter "document" has 0% schema description coverage, and the description only says "in the document" without explaining the identifier format, whether omission means the active document, or what happens with an invalid reference. This is precisely the case where the description needed to compensate for the schema and did not.

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?

Uses a specific verb ("List") with two concrete resource types ("parametric expression and spreadsheet alias"), so an agent knows this is a read of parameter-like objects in a document. It does not explicitly contrast itself with the sibling set_parameter, but the list-vs-set distinction is legible from the wording.

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?

The description gives no when-to-use guidance: it never says to call this before modifying values, nor mentions any alternative such as set_parameter or recompute. The agent must infer that this is a discovery step preceding a mutation call.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.