Skip to main content
Glama

Order a 3D print

how_to_order_a_print
Read-onlyIdempotent

How a buyer gets their own 3D model printed and shipped: the page to upload it, accepted files, and what happens next. Use this when someone has an STL or 3MF and wants it printed.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already establish this is a safe, read-only, idempotent, closed-world operation, so the description only needs to add content scope — and it does, listing the three things the answer covers. It doesn't clarify that the response is static guidance text rather than live data, which is a minor gap.

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?

Two sentences, no filler: the first defines content, the second defines the calling condition. The value proposition is front-loaded and every clause carries information.

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?

For a zero-parameter informational tool with full annotation coverage, the description says enough to call it correctly and to know what the answer contains. With no output schema, a brief note on the response shape (static guidance vs. live listing data) would have closed the loop.

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?

The tool takes zero parameters, so there is nothing for the description to disambiguate; baseline of 4 applies. Nothing in the text contradicts or misrepresents the empty schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names the exact content the tool returns (the upload page, accepted file types, and the post-upload flow) rather than restating the name. It reads as a guidance/answer tool, distinct from action siblings like complete_model_upload or estimate_job_price.

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

Usage Guidelines4/5

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

"Use this when someone has an STL or 3MF and wants it printed" gives a concrete trigger condition tied to file format and buyer intent. It stops short of naming follow-on alternatives (e.g., pricing or shop lookup), so no exclusions or routing are provided.

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