Skip to main content
Glama
FreeCAD Tutor MCP
by alex-r-t

tracked_recompute

Read-onlyIdempotent

Recompute a FreeCAD document and report newly introduced, resolved, and persistent object errors so you can track modeling changes and diagnose issues.

Instructions

Recompute the document and report new, resolved, and persistent object errors.

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

Input Schema

NameRequiredDescriptionDefault
doc_nameNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so the safety profile is covered. The description adds the useful detail that results are categorized into new/resolved/persistent errors, but says nothing about whether recompute forces a full rebuild, how long it may take, or that it changes document computed state.

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?

One sentence, front-loaded with the action and followed by the outcome categories; no filler or redundant restatement.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/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, and the tool is simple with only one parameter. The remaining gap is the ambiguity of doc_name's default behavior, which neither schema nor description resolves.

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?

The single parameter doc_name has zero schema description coverage and an empty-string default, and the description only says 'the document' without clarifying whether an omitted value targets the active document or an empty name. With 0% coverage the description should have compensated and does 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?

States a specific verb (recompute) and resource (the document) plus what the result contains: new, resolved, and persistent object errors. That error-triage framing distinguishes it from siblings like explain_freecad_error or get_sketch_diagnostics, though it never names an alternative outright.

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?

The 'new, resolved, persistent' phrasing implies this is called after model edits to re-check error state, but there is no explicit when-to-use statement, no prerequisite (e.g. an open document), and no named alternative tool.

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