salome-mcp

Overview Schema Source Related Servers Discussions Admin

create_box

Create a GEOM box by specifying dx, dy, and dz. This tool produces a box primitive for use in CAD geometry construction and meshing.

Instructions

Create a GEOM box by dimensions.

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": {
      "dx": "<dx>",
      "dy": "<dy>",
      "dz": "<dz>"
    },
    "name": "create_box"
  }
}

Input Schema

Name	Required	Default
`dx`	Yes
`dy`	Yes
`dz`	Yes
`name`	No	Box

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Aug 1, 2026

TDQS

B3.1/5.0

Behavior2/5

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

With no annotations available, the description carries sole responsibility for behavioral disclosure. It only states 'Create' without mentioning side effects, return values, or how the box integrates with the study environment, leaving significant behavioral ambiguity.

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, concise sentence that immediately communicates the core action without extraneous information. It is well-structured and front-loaded, making it easy for an agent to quickly understand the tool's purpose.

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 no annotations, no parameter descriptions, and just a minimal sentence, the overall description is incomplete. It lacks essential context about how the box is represented, what the output contains, and any dependencies or side effects, making it insufficient for an agent to fully understand the tool's behavior.

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?

Schema description coverage is 0%, so the description must compensate for parameter clarity. The phrase 'by dimensions' hints that dx, dy, dz relate to dimensions, but it does not explicitly map each parameter (e.g., length, width, height) or specify units, leaving the schema's bare numeric fields inadequately explained.

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 function as creating a GEOM box using dimensions, with a specific verb ('Create') and resource ('GEOM box'). It effectively distinguishes itself from sibling shape-creation tools like create_cylinder and create_sphere by focusing on box creation via dimensions.

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 usage guidance is provided regarding when to use this tool compared to alternatives such as create_cylinder or create_sphere. There are no explicit exclusions or contextual cues beyond the obvious purpose of creating a box.

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