salome-mcp

Overview Schema Source Related Servers Discussions Admin

rotate_object

Rotate an existing GEOM object around a chosen axis (X, Y, or Z) by a specified angle in degrees. Modifies the geometry directly, eliminating the need to create a new copy.

Instructions

Rotate a GEOM object in place around X/Y/Z axis (degrees, no new copy).

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": {
      "source_ref": "<source_ref>",
      "angle_degrees": "<angle_degrees>"
    },
    "name": "rotate_object"
  }
}

Input Schema

Name	Required	Default
`axis`	No	Z
`source_ref`	Yes
`angle_degrees`	Yes

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Aug 1, 2026

TDQS

A3.9/5.0

Behavior4/5

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

With no annotations, the description discloses the critical behavioral trait that it modifies the object in place rather than creating a new copy. It also specifies the rotation axis and angle in degrees. However, it does not mention whether the rotation is reversible or whether it rotates about the object origin or global origin.

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 a single sentence that gets directly to the point. It front-loads the action and includes only essential qualifiers ('in place', 'no new copy') with no filler.

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?

The description covers the core mutation behavior but omits important context such as the pivot point for rotation (e.g., object origin vs. global origin) and any preconditions. Since the tool has an output schema, return values are likely covered, but the missing pivot information could affect correct usage.

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?

The description explains the 'axis' and 'angle_degrees' parameters by mentioning X/Y/Z axis and degrees, respectively. However, the required 'source_ref' parameter is not addressed at all, leaving ambiguity about what it refers to. With 0% schema coverage, the description should compensate more fully.

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 verb 'Rotate', the resource 'GEOM object', and the key distinguishing feature 'in place, no new copy', which differentiates it from copy/duplicate tools. It also specifies the axis and angle units, making the purpose unambiguous.

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

Usage Guidelines3/5

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

The description implies its use for rotating existing geometry but does not explicitly state when to choose it over alternatives like translate_object or copy_object. There are no explicit exclusions or alternative recommendations, so it relies on implication.

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