Skip to main content
Glama
freecad-mcp-headless

freecad-mcp-headless

by pitbuild

recompute

Re-evaluate a CAD document's timeline after external changes to update dependent features and keep the headless FreeCAD model consistent.

Instructions

Re-evaluate the document timeline after external changes.

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": "recompute"
  }
}

Input Schema

NameRequiredDescriptionDefault
documentNo

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 at all, the description carries the full behavioral burden and falls well short: it does not say whether recompute mutates stored document state, whether it is reversible, whether it can fail on invalid geometry, or how long it may take. Only the trigger condition is disclosed; the effects are left entirely implicit.

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 front-loaded sentence with no filler or redundancy. It is efficient, though efficiency here partly reflects under-specification rather than disciplined editing.

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?

For a mutation-style tool with one undocumented optional parameter, no annotations, and no output schema, the description should at minimum cover default behavior when document is omitted and what state changes afterward. Neither is present, so an agent cannot call this correctly in ambiguous cases.

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?

There is one parameter, document, with 0% schema description coverage and a default of null, and the description never mentions it. Critically, it does not explain what omitting document means (active document? all open documents?), which is the single most important semantic an agent needs before calling.

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?

"Re-evaluate the document timeline after external changes" names a verb (re-evaluate) and an object (document timeline), but "timeline" is figurative and never grounded in concrete terms (recomputing feature/parametric dependencies). It also draws no boundary against siblings such as inspect_document or open_document, so an agent must guess what distinguishes a recompute from a re-inspection.

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?

"After external changes" gives a genuine trigger condition, which is more than nothing, but there is no statement of when not to use it, no prerequisite (e.g., document must be open), and no named alternative for read-only inspection of the same state.

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