Skip to main content
Glama
freecad-mcp-headless

freecad-mcp-headless

by pitbuild

bounding_box

Calculates a CAD model's overall extents, minimum, maximum, and centre in millimetres to support measurement and placement checks.

Instructions

Return the bounding box size, minimum, maximum and centre in millimetres.

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

Input Schema

NameRequiredDescriptionDefault
documentNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3/5.0
Behavior3/5

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

With no annotations supplied, the description carries the full burden, and it does disclose the computed outputs and the unit convention (millimetres), which is real added value. It omits behavioral context such as whether the target must be an open/active document, how assemblies or multi-body documents are handled, or what happens when nothing is loaded.

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 that names the outputs and the unit without filler. Nothing here is redundant or buried.

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 query tool with no annotations and no output schema, the description should at minimum explain the document parameter and the open-document requirement. As written, an agent cannot determine what to pass or what precondition must hold before calling.

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', optional, defaulting to null) with 0% schema description coverage, and the description says nothing about it. It does not clarify whether null means the active document or whether a full path/name is expected, leaving the only parameter's semantics entirely undefined.

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 ('Return') and a specific resource ('bounding box'), and enumerates exactly what is reported: size, minimum, maximum and centre. An agent can tell this is a geometry query distinct from action-oriented siblings like recompute or save_document, though it never names a sibling to contrast against.

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, no prerequisites (e.g. whether a document must be open or active), and no indication of when an alternative such as measure or inspect_document would be preferred. The agent must infer everything.

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