Skip to main content
Glama

kernelcad

by com.kernelcad

Solve Mates

solve_mates
Read-only

Use this when you need to solve the mate graph and get part poses. Run the v0.6 mate-graph solver on the active assembly. Returns { status, poses, iterations? } where each pose is a serialized Transform ({ translation, rotateAxis, rotateDeg }). Optional poses overrides mate pose values by mate name.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
posesNoOptional numeric pose overrides keyed by mate name.
assemblyNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
okYes
errorNo
posesNoSolved part poses keyed by mate; each a serialized Transform (success).
statusNoSolver status (success).
errorCodeNo
errorHintNo
iterationsNoSolver iteration count (success).

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, and the description adds some behavioral detail (e.g., 'Run the v0.6 mate-graph solver on the active assembly'). The description does not contradict annotations, but it adds limited extra information beyond acknowledging the read-only nature.

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?

The description is concise, two sentences long, and front-loaded with the primary purpose. Every sentence adds value without unnecessary words.

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?

While the description covers the return format and has an output schema, it fails to explain the 'assembly' parameter, which is crucial for context (active assembly). This omission reduces completeness for a tool with two parameters.

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 input schema has two parameters: 'poses' (described in schema) and 'assembly' (undescribed). The description only repeats the schema description for 'poses' and does not explain the 'assembly' parameter, leaving a gap in parameter understanding despite 50% schema coverage.

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 clearly states the tool's purpose: 'solve the mate graph and get part poses' using the v0.6 mate-graph solver. It specifies the action (solving), the target (mate graph), and the outcome (part poses), distinguishing it from siblings like add_mate or solve_sketch.

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?

The description begins with 'Use this when you need to solve the mate graph and get part poses,' providing clear usage context. However, it does not explicitly mention when not to use this tool or list alternative tools for similar tasks, such as solve_sketch.

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

All kernelcad toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A3.9/5.0
Disambiguation4/5

Tools are mostly distinct, with clear descriptions for each. However, there is some potential overlap between inspection tools like 'inspect' and 'mesh_summary', and between rendering tools 'render_preview' and 'get_latest_render', which could cause minor confusion.

Naming Consistency5/5

All tool names follow a consistent snake_case verb_noun pattern, making it predictable for an agent to infer functionality.

Tool Count2/5

44 tools is significantly higher than the typical well-scoped range of 3-15. While the domain is complex, the count feels excessive and could overwhelm an agent.

Completeness4/5

The tool set covers an extensive range of CAD operations including creation, inspection, rendering, export, and verification. Minor gaps exist, such as direct sketch editing tools, but overall it is comprehensive.

Resources