salome-mcp

by gnshb

Overview Schema Source Related Servers Discussions Admin

Python

Local

boolean_operation

Apply fuse, cut, or common boolean operations to base and tool objects to combine or subtract CAD geometries.

Instructions

Perform boolean operation on GEOM objects.

operation: fuse | cut | common base_object/tool_objects: entry IDs or object names

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": {
      "operation": "<operation>",
      "base_object": "<base_object>",
      "tool_objects": "<tool_objects>"
    },
    "name": "boolean_operation"
  }
}

Input Schema

Name	Required	Default
`operation`	Yes
`base_object`	Yes
`result_name`	No	BooleanResult
`tool_objects`	Yes

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Aug 1, 2026

TDQS

C2.9/5.0

Behavior2/5

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

With no annotations, the description carries full responsibility for behavioral disclosure, but it does not mention side effects, whether objects are modified in place or new objects are created, or any requirements like existing geometry. This lacks transparency for a mutation-like 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 concise and front-loaded with the main purpose. The parameter summary is useful and not verbose. It could be slightly better organized but is appropriately sized.

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?

For a tool with 4 parameters, no schema descriptions, and no annotations, the description is under-specified. It lacks details on result_name, the exact behavior of the operation, and prerequisites or side effects. The presence of an output schema helps, but the description still leaves significant gaps.

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 partially compensates for the 0% schema coverage by explaining the operation values (fuse|cut|common) and that base_object/tool_objects accept entry IDs or names. However, it omits the result_name parameter entirely and does not clarify the array format of tool_objects, so the compensation is incomplete.

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?

The description clearly states the tool performs boolean operations on GEOM objects, naming the specific operations (fuse, cut, common). It distinguishes the general purpose from the more specific sibling tools, though it does not explicitly refer to them.

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?

No guidance is provided on when to use this generic boolean_operation tool versus the dedicated fuse_objects, cut_objects, or common_objects tools. The description implies it can handle any of the three operations but doesn't advise on choice.

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