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

find_faces

Read-onlyIdempotent

Locate face names on a FreeCAD shape by normal direction, area, surface type, or proximity to a point, so you can target the correct face for selection and modeling steps.

Instructions

Find FaceN names on a shape matching normal ('+Z', '-Z', 'X'), area, surface type, or point.

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": {
      "object_name": "<object_name>"
    },
    "name": "find_faces"
  }
}

Input Schema

NameRequiredDescriptionDefault
areaNo
normalNo
doc_nameNo
max_areaNo
min_areaNo
near_pointNo
object_nameYes
max_distanceNo
surface_typeNo
select_matchesNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

C2.8/5.0
Behavior2/5

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

Annotations already declare read-only, idempotent, closed-world, non-destructive behavior, so safety is covered. The description adds nothing about how multiple filters combine (AND vs OR), filter precedence, result limits, or that select_matches may change the application's current selection state despite readOnlyHint.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single front-loaded sentence with no padding, which is good, but the parenthetical quoting of normal values is awkward and the brevity comes at the cost of substance rather than efficiency.

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?

With 10 parameters at 0% schema coverage and no output-schema explanation needed, the description should carry the filter semantics; instead it leaves the combination rules, the required object_name, and the selection side effect unexplained. An agent could invoke it but would likely guess at parameter interactions.

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

Parameters3/5

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

Schema description coverage is 0% across 10 parameters, so the description must compensate; it only glosses normal (with '+Z'/'-Z'/'X' examples), area, surface type, and point. It says nothing about doc_name, max_distance, min_area/max_area precedence, or select_matches, leaving half the surface undocumented, though the normal-format examples are genuinely useful.

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 (find) and resource (FaceN names on a shape) with the qualifying criteria listed. It is clearly distinguishable from the sibling find_edges, though the term 'FaceN names' is slightly opaque without prior FreeCAD knowledge.

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?

There is no guidance on when to use this versus find_edges, analyze_shape, or get_selection, and no statement of prerequisites such as needing an existing document or shape. The criteria list implies a search but never tells the agent when a face search is the right approach or what to do with the results.

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