Skip to main content
Glama

place_and_mate

Position a component at an exact target pose and create mates to capture the intended assembly branch, with verification that the pose is held after mating.

Instructions

Posicionar y matear — pose a component exactly, THEN create its mates.

The branch-safe mating recipe: angle/distance mates are bistable (two solutions; rebuilds can flip to the mirror). Creating each mate while the component already sits at the exact target pose makes the solver capture the intended branch. After the mates, the pose is read back and compared against the request — pose_held=False means a mate pulled the component elsewhere (wrong branch / conflicting mate): fix it, don't trust it.

Args: component_name: Instance name from get_active_assembly_info. origin_mm / rotation_rows: Exact target pose (see move_component). mates: Ordered mate specs, each {"type": "coincident"|"concentric"|"distance"|"angle", "entity1_id": ..., "entity2_id": ..., "component2_name": ..., # the mate partner "align": "ALIGNED"|"ANTIALIGNED", # optional "distance_mm": float, "angle_deg": float} # per type pose_tolerance_mm: Max |Δorigin| per axis for pose_held (default 0.1).

Returns {pose_before, mates, pose_after, pose_held}.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
matesNo
origin_mmYes
rotation_rowsNo
component_nameYes
pose_tolerance_mmNo
Behavior5/5

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

With no annotations, the description fully discloses critical behaviors: bistable nature of angle/distance mates, rebuild flipping risk, and the purpose of the pose_held check. This provides deep insight into the tool's operation.

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 description is well-structured with a summary, then detailed explanation, then an Args list. It is slightly verbose but every sentence contributes value. Could be tightened slightly without losing information.

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?

Given the complexity (combined position + mate) and lack of output schema, the description covers the purpose, parameters, and behavioral output (pose_held check). It could detail the return structure more but is largely adequate.

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

Parameters5/5

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

The schema has 0% description coverage, but the description adds detailed meaning for each parameter, including the structured format for mates with fields like type, entity1_id, align, etc. This compensates fully for the schema gap.

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 dual action: 'pose a component exactly, THEN create its mates.' This distinguishes it from sibling tools like add_*_mate and move_component, which only handle one aspect.

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 'branch-safe mating recipe' explains when to use this tool (for precise positioning before mating) and what to look for after (pose_held flag). It lacks explicit when-not-to-use but the context is clear.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/danielproxd2/MCP_CAD'

If you have feedback or need assistance with the MCP directory API, please join our Discord server