Skip to main content
Glama
Sign In

Maglev Parts

by com.trymaglev
OverviewDiscussionsAdmin

Place a production order (paused)

place_order
Destructive

Ordering through the API is paused: this tool always refuses and orders, pays and sends nothing. Call preview_order instead and show the user its terms; to order, the user sends the quote_id to Maglev. We quote you one price for the build, fixed before you commit. Every number you pay is on that quote.

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": {
      "quote_id": "<quote_id>"
    },
    "name": "place_order"
  }
}

Input Schema

NameRequiredDescriptionDefault
quote_idYesquote_id of one offer returned by get_quotes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior2/5

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

The annotations declare destructiveHint=true, readOnlyHint=false and openWorldHint=true, but the description of this tool contradicts them by saying it refuses every call, orders nothing, pays nothing and sends nothing; in practice this is a no-op read. The description is unusually informative about side effects, but in this case it directly contradicts structured annotations.

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 pause notice is front-loaded and the action to take comes next, which good structure. The closing two sentences about fixed pricing read as promotional filler and do not earn their place in a definition for a blocked tool.

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?

For a one-parameter, non-functional tool with no output schema, the description covers everything an agent needs: that calls fail, what to call instead, and what the user must do out-of-band. Nothing needed to behave correctly is missing.

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?

Schema coverage is 100%, and the schema already says quote_id comes from get_quotes. The description adds pricing context (one fixed quote price, every number paid is on the quote), but does not explain how quote_id would be used here, which is moot because the tool refuses all input. It beats the baseline slightly, but only just.

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 (place a production order) and immediately clarifies the tool's real behavior: the API is paused, so it always refuses and orders, pays and sends nothing. That makes it unambiguously distinguishable from the sibling it names, preview_order.

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 an explicit substitute ('Call preview_order instead and show the user its terms') plus the real ordering path ('the user sends the quote_id to Maglev'). The when-not-to-use case is stated first, so an agent cannot mistake this for the ordering action.

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

All Maglev Parts 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