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

find_edges

Read-onlyIdempotent

Locate edge names on a FreeCAD shape by direction, length, curve type, or proximity, then optionally select matching edges for modeling or inspection.

Instructions

Find EdgeN names on a shape matching direction ('X'/'Y'/'Z'/'+Z'/'-Z'), length, or location.

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_edges"
  }
}

Input Schema

NameRequiredDescriptionDefault
lengthNo
doc_nameNo
directionNo
curve_typeNo
max_lengthNo
min_lengthNo
near_pointNo
object_nameYes
max_distanceNo
select_matchesNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

C2.9/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint=false and destructiveHint=false, so the safety profile is covered. The description adds only that results are edge names, and it omits the select_matches side effect (which changes UI selection state) and any behavior when no match is found; the output schema covers return shape.

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 compact sentence that front-loads the verb, resource, and filter criteria. No redundant wording, though the parenthetical direction literals make the sentence dense.

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 zero schema description coverage, the description should explain the matching semantics (exact length vs. range, direction tolerance, radius for near_point), but it does not. It is also silent on required object_name and the select_matches toggle, so an agent cannot infer correct invocation from description plus schema alone.

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?

Schema coverage is 0% across 10 parameters, and the description only hints at direction (with useful literal values 'X'/'Y'/'Z'/'+Z'/'-Z'), length, and location. It never explains curve_type, min_length/max_length, near_point/max_distance pairing, doc_name, or select_matches, leaving most parameters undocumented anywhere.

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 and resource: 'Find EdgeN names on a shape', plus the matching criteria (direction, length, location). It is distinguishable from find_faces by naming edges specifically, though it never explicitly contrasts with that sibling.

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 implies the tool retrieves edge names for filtering, but gives no when-to-use guidance, no prerequisites (selection or active document), and no mention of alternatives like find_faces or how this pairs with fillet_edges/chamfer_edges.

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