AIURION Agentic 3D Printing — San Francisco

Prepare Enclosure

prepare_enclosure

Read-only

Prepare or revise an enclosure from KiCad PCB text or dimensions. Returns exact parameters, review revision, warnings and editable customer review URL. Uses a guest token but no quote allowance. No manufacturing or purchase occurs.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "prepare_enclosure"
  }
}

Input Schema

Name	Required	Description
`kicadPcb`	No	KiCad 6–9 .kicad_pcb UTF-8 text. Sent to AIURION for parsing; raw PCB text is not stored in the draft or review link. Use parameters instead for dimensions.
`quantity`	No	Number of complete sets to prepare or quote.
`parameters`	No	Workbench geometry parameters. Use the returned normalized values for review and quoting.
`accessToken`	No	Guest token returned by printing.sessions.start. Optional when Authorization already carries a permanent key or guest token.

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

AddedOct 15, 2026

TDQS

A4/5.0

Behavior4/5

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

Annotations already cover readOnly/non-destructive/closed-world, but the description adds genuinely new context: the guest-token auth path, that no quote allowance is consumed, and that no manufacturing or purchase occurs. It also states what comes back (normalized parameters, review revision, warnings, editable review URL). Minor tension with readOnlyHint=true given that a revision and review link are produced.

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?

Four short sentences, front-loaded with what the tool does, followed by return content, auth/cost implications, and side-effect scope. Every sentence carries distinct information with no filler.

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?

For a tool with a large nested parameter object, an output schema, and full annotation coverage, the description is nearly complete: it flags input alternatives, auth, cost, and that no fulfillment occurs. It could note that at least one geometry source (kicadPcb or parameters) is expected, since no parameters are required.

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?

Schema description coverage is 100% at the top level, so the schema already documents kicadPcb, quantity, parameters, and accessToken. The description only restates the input alternatives ('KiCad PCB text or dimensions') without adding format, precedence, or interaction rules beyond the schema. Baseline 3 applies.

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 states a specific verb set (prepare or revise) and resource (enclosure), plus the accepted input forms (KiCad PCB text or dimensions). It implicitly separates itself from the sibling quote_enclosure by noting 'no quote allowance', though it never names the sibling. Clear purpose, only weak explicit sibling differentiation.

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?

It gives clear conditions: use a guest token, this call does not consume quote allowance, and no manufacturing or purchase results — which effectively routes quoting workflows to the quote_* siblings. It stops short of naming quote_enclosure or quoting a session prerequisite, so no explicit alternatives list.

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

All AIURION Agentic 3D Printing — San Francisco tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?