Skip to main content
Glama
Sign In

step2gcode

by com.step2gcode
OverviewDiscussionsAdmin

get_download_link

Idempotent

Return the download link for the finished G-code. THIS is the billed step: one credit per model not paid for yet. Re-downloading the same job or a model already paid for is free.

Called without confirm, this tool charges nothing and only reports what the download would cost. Show that to the user, wait for their answer, and only then call again with confirm=true. Never set confirm=true on your own initiative - it spends the user's money.

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": {
      "job_id": "<job_id>"
    },
    "name": "get_download_link"
  }
}

Input Schema

NameRequiredDescriptionDefault
job_idYes
confirmNoSet to true only after the user has explicitly agreed to spend the credit.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior4/5

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

Beyond the annotations it discloses the billing model: one credit per unpaid model, free re-downloads of the same job, and zero charge when confirm is omitted. That is real cost/auth context the annotations only hint at via the title. It stops short of saying what happens if the job is not finished or how an insufficient balance is reported.

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 is returned and what it costs, followed by the required call sequence. Nothing is padded and the money-risk warning is placed where it cannot be missed.

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 correctly states the primary return value and the dry-run cost report. Only edge cases (job not finished, duplicate job ids, balance errors) are left uncovered, which is acceptable for a two-parameter 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 50%: confirm is documented in the schema, job_id is not. The description compensates by explaining the confirm semantics operationally (no charge vs. spending a credit) and implicitly ties job_id to a job/model that may already be paid for, which is meaning the schema does not supply.

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 concrete verb and resource ('Return the download link for the finished G-code') and the resource noun itself separates it from the sibling that returns a STEP download link. No ambiguity about what comes back.

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?

Gives an explicit two-step protocol: first call without confirm to quote the cost, show it to the user, wait, then call again with confirm=true. It also states a hard prohibition ('Never set confirm=true on your own initiative'), which is exactly the when-not guidance an agent needs.

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

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