Skip to main content
Glama

Upload a 3D model from this computer

start_model_upload

For agents that can read local files (Claude Code, Cursor): returns a signed URL to PUT an STL or 3MF to, with the exact headers to send. After the upload, call complete_model_upload. Chat apps should use stage_model_from_url instead. Needs a connected Printlooper account.

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": {
      "filename": "<filename>",
      "size_bytes": "<size_bytes>"
    },
    "name": "start_model_upload"
  }
}

Input Schema

NameRequiredDescriptionDefault
filenameYesMust end in .stl or .3mf
size_bytesYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Beyond the annotations, it discloses the prerequisite (a connected account), the two-step flow (start upload, then complete), and that the response contains a signed URL plus exact headers. It does not mention URL expiry or other limits, but the 50 MB cap is already in the schema constraints.

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?

Three short sentences, front-loaded with the audience restriction, then the return value, then the required follow-up. Every sentence resolves a distinct decision an agent must make.

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, so the description carries the response shape, which it does by describing the signed URL and headers. For a two-parameter, non-idempotent upload step, this covers audience, prerequisites, return value, and the next call.

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?

The schema coverage is only 50%: filename carries a format restriction, while size_bytes has only numeric bounds. The description reinforces accepted file types (STL/3MF) but adds no format or unit meaning beyond what the schema already documents.

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?

The description states a specific verb and resource: it returns a signed URL for PUT-ing an STL or 3MF file, along with the exact headers to send. It distinguishes itself from both siblings by naming complete_model_upload as the required follow-up and stage_model_from_url as the alternative for chat apps.

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?

It gives explicit routing: use this tool when the agent can read local files (Claude Code, Cursor), and use stage_model_from_url in chat apps. It also names the mandatory next step (complete_model_upload) and states the prerequisite of a connected Printlooper account.

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