Skip to main content
Glama

step2gcode

convert_mesh_to_step

Turn an uploaded STL or 3MF mesh back into a STEP solid with exact surfaces - planes, cylinders, cones and fillets instead of triangles, intersected into real edges. Free; only the download of the finished file is charged.

Use this when the user has a mesh and needs CAD geometry: a hole becomes a cylinder with a diameter again, a chamfer a cone with an angle, so the part can be dimensioned, modified and machined. Typical case: the CAD source is gone and the mesh is all that is left.

The answer states the largest measured deviation between the built solid and the mesh, in millimetres - always pass that number on to the user, it is what tells them whether the result is accurate enough for their part. Parts made of freeform surfaces and raw 3D scans are rejected with a reason instead of being badly reconstructed.

Upload the mesh the same way as any other file (curl to /api/upload, upload_file_content or create_upload_link), then pass the file_id here. The resulting STEP file can go straight into generate_gcode afterwards.

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": {
      "file_id": "<file_id>"
    },
    "name": "convert_mesh_to_step"
  }
}

Input Schema

NameRequiredDescriptionDefault
file_idYesfile_id of an uploaded .stl or .3mf mesh

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.8/5.0
Behavior5/5

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

Goes well beyond the annotations by disclosing cost semantics ('Free; only the download of the finished file is charged'), the failure mode (rejected with a reason rather than badly reconstructed), and the returned accuracy figure in millimetres. That tells the agent both the risk profile and how to relay results to the user.

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?

Front-loaded with the core action and result, then cost, usage, and workflow. Four paragraphs is on the long side, and the hole/chamfer illustration partly repeats the surfaces claim, but almost every sentence carries actionable information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a single-parameter conversion tool with no output schema, the description supplies the return value (largest measured deviation in mm, with instruction to pass it on), the error behavior, the pricing model, and the upstream/downstream tool sequence. Nothing an agent needs to invoke and report on this tool is missing.

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

Parameters4/5

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

Schema coverage is 100% and the schema already labels file_id as an uploaded .stl/.3mf mesh, so baseline is 3. The description adds real value by naming the concrete upload paths (curl to /api/upload, upload_file_content, create_upload_link) that produce a valid file_id.

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?

States a specific verb and resource plus formats: 'Turn an uploaded STL or 3MF mesh back into a STEP solid with exact surfaces', and explains the qualitative result (planes, cylinders, cones, fillets instead of triangles). An agent can tell this apart from sibling file/job tools without opening the schema.

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

Usage Guidelines5/5

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

Explicit when-to-use ('when the user has a mesh and needs CAD geometry'), a typical scenario (CAD source gone), when-not (freeform surfaces and raw 3D scans are rejected), and the surrounding workflow: upload via upload_file_content or create_upload_link first, then generate_gcode afterwards.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources