Skip to main content
Glama
FullyDefined – AI for SOLIDWORKS

FullyDefined – AI for SOLIDWORKS

fit_spline

Replaces a connected chain of lines and arcs in an open sketch with one spline within a tolerance, leaving originals as construction geometry for a single-face track before extrusion.

Instructions

In the open sketch, replace a chain of lines and arcs with ONE spline that follows them within a tolerance (default 0.001 mm). The entities must form one connected chain; they stay as construction geometry. Use it before extrude_surface when a track has to be a single face that points can be mated to along its whole length.

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

Input Schema

NameRequiredDescriptionDefault
unitNoUnit of the tolerance (mm, cm, m, inch or ft)
toleranceNoHow far the spline may be from the entities (default 0.001 mm)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.9/5.0
Behavior3/5

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

No annotations are supplied, so the description carries full responsibility for behavioral disclosure. It does disclose two important behaviors: the entities must form one connected chain, and they remain as construction geometry after conversion. It does not say whether the original chain is consumed or duplicated, whether the edit is reversible, or what happens when the chain is not connected, so this is incomplete for a mutation tool.

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?

The content is front-loaded: the core action comes first, then the constraint, then the downstream use. Every sentence adds value. The third sentence is dense and telegraphic ('a track has to be a single face'), which costs a little clarity, but it is not padding.

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

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a two-optional-parameter tool with no output schema and no annotations, the definition covers what the tool does, the prerequisite, the tolerance, and the intended workflow. It omits the failure behavior when the tolerance cannot be met and whether the change can be undone, which keeps it from being fully complete.

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 coverage is 100%, so both parameters are already documented in the schema, including the tolerance default. The description only reinforces the tolerance concept ('follows them within a tolerance (default 0.001 mm)') and says nothing about unit handling, which is the baseline-3 case.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names a specific verb and resource: replace a chain of lines and arcs with ONE spline within a tolerance. It also states where the entities come from (an open sketch) and how the result is used, so an agent can tell it apart from siblings such as extrude_surface.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives clear context for when to use the tool ('before extrude_surface when a track has to be a single face that points can be mated to along its whole length') plus the prerequisite that the entities must form one connected chain. It does not name an alternative approach for the same job, so it falls short of a 5.

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

Deploy Server

Other Tools