Skip to main content
Glama

Export STEP (a job)

export_step

Export a SAVED project as STEP — real B-rep, not a mesh, for CAD interchange. OCCT takes minutes, so this runs as a JOB: call with projectId to get a jobId, then call again with that jobId alone until status is "done", waiting retryAfterMs between polls (polling faster burns your call budget). A poll reports waitingMs; a job still "queued" after a few minutes is stuck, so stop polling and start a new one. Needs a saved project — run save_project first; it cannot export an inline tree. Pro accounts only.

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": "export_step"
  }
}

Input Schema

NameRequiredDescriptionDefault
fitNoFit analytic curved surfaces (cylinders, cones, spheres, tori) instead of flat facets. Default false.
jobIdNoA handle from an earlier call. Send it ALONE to poll.
projectIdNoThe saved project to export. Omit when polling.
keepFacetsNoKeep a SET facet count as flat faces: a cylinder, cone, tube or sphere whose side count was set (a hexagonal nut trap, a .scad sphere($fn=8)) exports with the flat faces its STL has, while an automatic count stays a true curved surface. Default true, as in the editor; false exports every round shape curved.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / fit / description
      Previous value: -"Beta: fit analytic curved surfaces (cylinders, cones, spheres, tori) instead of flat facets. Default false."New value: +"Fit analytic curved surfaces (cylinders, cones, spheres, tori) instead of flat facets. Default false."
  2. Changed1 schema field changed
    • changedInput schema / properties / fit / description
      Previous value: -"Fit analytic surfaces (cylinders, planes) instead of emitting a faceted solid. Default false."New value: +"Beta: fit analytic curved surfaces (cylinders, cones, spheres, tori) instead of flat facets. Default false."
  3. Changed1 schema field changed
    • addedInput schema / properties / keepFacets
      Added value: +{
      +  "description": "Keep a SET facet count as flat faces: a cylinder, cone, tube or sphere whose side count was set (a hexagonal nut trap, a .scad sphere($fn=8)) exports with the flat faces its STL has, while an automatic count stays a true curved surface. Default true, as in the editor; false exports every round shape curved.",
      +  "type": "boolean"
      +}
  4. First observed

TDQS

A4.8/5.0
Behavior5/5

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

Annotations only say this is a non-readonly, non-idempotent, non-destructive write; the description explains why — it enqueues an asynchronous OCCT job that takes minutes, requires polling with retryAfterMs, burns call budget if polled too fast, and reports waitingMs, with stuck-job recovery guidance. That is exactly the behavioral context annotations cannot carry.

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?

Front-loaded with what the tool produces, then the job protocol, then prerequisites, then the account constraint — each sentence adds a distinct operational fact. Parenthetical cost warnings are short and earn their space.

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?

With no output schema, the description covers the job envelope (jobId, status, retryAfterMs, waitingMs) well, which is what an agent most needs. It stops short of saying how the finished STEP file is retrieved or where it lands after status is 'done', which is the one gap left for an export tool.

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 already 100%, including per-flag detail for keepFacets and fit, so the baseline is 3. The description adds value by establishing the mutually exclusive lifecycle of projectId vs. jobId (initial submit versus poll loop) as a workflow rather than two isolated fields, though it does not touch fit/keepFacets since the schema handles those.

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?

Names a specific verb and resource ('Export a SAVED project as STEP') and immediately qualifies the output semantics ('real B-rep, not a mesh, for CAD interchange'), which separates it from the mesh/Render/export_2d siblings without naming them. An agent knows exactly what this produces versus a generic export.

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?

Explicitly routes the caller: use save_project first, inline trees are not supported, Pro accounts only, and the two-phase call pattern (projectId → jobId, then jobId alone) is spelled out with a polling cadence and a stop condition for stuck queued jobs. Exclusions and prerequisites are all present.

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