Maglev Parts

Get manufacturing quotes from shops

get_quotes

Use this when the user wants prices or lead times for making their uploaded parts: a CNC, sheet metal, injection molding or wire harness quote. Asks these shops in parallel, and the user's CAD file goes to them: CNC machining, Make Parts Now (US) plus AFN network shops; sheet metal, RMFG (US) plus AFN network shops; injection molding, SSG MFG's budgetary molding estimate (US) plus AFN 3D-printing offers for the same file, which come back as process 3d_printing; wire harness, MiniProto (US). AFN offers give each shop's ship-from country. Returns parts[], each with offers[] in one shape: shop, price_type (firm or budgetary), total_usd, one_time_costs, lead_time_days, ships_by, quote_id. Show the user every offer; do not pick a winner for them. To see what ordering one would cost and how, pass its quote_id to preview_order. For catalog parts, use build_rfq. Requires a Maglev API key.

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": {
      "file_ids": "<file_ids>",
      "quantity": "<quantity>"
    },
    "name": "get_quotes"
  }
}

Input Schema

Name	Required	Description
`sort`	No	How to order each part's offers. Default price.
`options`	No	Optional per-file options: { file_id: { material, finish, tolerance_mm, wall_mm, draft_deg, speed } }. finish: CNC standard\|anodized\|polished\|bead_blasted, sheet metal as_cut\|deburred\|anodized\|powder_coat. Each offer reports finish_applied; shops that ignore an option say so.
`file_ids`	Yes	file_id values returned by the upload commands from upload_cad_for_quote
`quantity`	Yes	Units per part, unless overridden per file in options.quantity
`processes`	No	Optional per-file process override: { file_id: process }

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 11, 2026

TDQS

A4.6/5.0

Behavior4/5

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

Annotations already declare openWorldHint=true and readOnlyHint=false, so external contact is expected; the description still adds crucial context by naming the external shops per process and warning that the user's CAD file is sent to them. It also discloses the API-key requirement and states the response shape in enough detail to act on. The main omission is whether quote_ids expire or how long shop responses take to arrive.

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?

Front-loaded with the trigger and alternative routing before the dense shop-by-process inventory. The routing sentences are long and run-on, but each carries actionable information (shop names, country of shipment, quote_id), so little could be cut without losing value.

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?

No output schema exists, yet the description enumerates parts[] and offers[] fields (shop, price_type, total_usd, one_time_costs, lead_time_days, ships_by, quote_id) so an agent knows what comes back. Given five parameters including two nested per-file objects, the definition covers trigger, side effects, external parties, and result shape adequately.

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 100%, so baseline would be 3, but the description adds routing semantics the schema cannot express: which shop network each process reaches, that AFN 3D-printing offers return as process 3d_printing even though it is not a schema enum value, and that options can be overridden per file. The sort parameter is left to the schema, which is acceptable at full coverage.

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 ('prices or lead times for making their uploaded parts') plus the four processes covered. It also explicitly distinguishes itself from siblings by naming preview_order and build_rfq with the conditions that select them.

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?

Opens with an explicit trigger ('Use this when the user wants prices or lead times'), routes catalog parts to build_rfq, and routes ordering-cost questions to preview_order via quote_id. It also sets a usage constraint ('Show the user every offer; do not pick a winner'), which is guidance an agent could not infer elsewhere.

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

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