step2gcode

create_upload_link

Create a short-lived link the user opens in their browser to upload a CAD file (STEP, DXF or SVG). Returns the link and an upload_id. Poll check_upload with the upload_id until it reports a file_id, then call generate_gcode. Free.

Before using this, check whether you can run shell commands. If you can, do not send the user to the browser: compress the file locally and pass it to upload_file_content (the compression is detected by itself). That works inside sandboxes without network access, which is the common case - a direct curl upload fails there with a proxy error. The response of this tool spells out all three routes in order.

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

Input Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 13, 2026

TDQS

A4.8/5.0

Behavior5/5

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

Annotations are minimal and only tell us that this is a non-read-only, non-destructive, non-idempotent, non-open-world call. The description adds information the annotations do not: the link is short-lived, the call is free, and a direct network upload fails in a sandbox with a proxy error. Those are the failure-mode and cost details an agent needs before choosing a route.

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 first paragraph is well front-loaded and covers the purpose, the sequence of calls, and the cost. The second paragraph is longer than it needs to be, and the final sentence ('The response of this tool spells out all three routes in order') restates rather than instructs and could be cut.

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?

There is no output schema, and the description compensates by naming the return values (link and upload_id) and describing the follow-on workflow through check_upload and generate_gcode. For a zero-parameter link-minting tool, an agent has everything it needs to select and call it correctly.

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?

This tool takes zero parameters, so the baseline score is 4. Schema coverage is 100% and there is nothing for the description to disambiguate. It still adds the relevant domain constraint, namely the three accepted file formats, which is beyond what an empty schema conveys.

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 ('Create a short-lived link') plus the resource being uploaded and the accepted formats (STEP, DXF, SVG), and states what is returned (link + upload_id). An agent can distinguish it from upload_file_content and get_download_link without opening either 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?

This definition explicitly tells when not to use it: if shell commands can be run, use upload_file_content instead. It also gives the ordering constraints: poll check_upload until a file_id appears, then call generate_gcode. That is the full when/when-not/alternative structure.

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

All step2gcode 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?