Skip to main content
Glama

KinetiCAD CNC Parts

Request an order

request_order

Send an order request for a part to KinetiCAD. Call this only after the user has seen the price and said yes, and has given a shipping address and an email address. It sends those details to KinetiCAD. No payment is taken: Bera Demirhan at KinetiCAD emails the user within 1 business day with the confirmed price and delivery date, and the user pays only after agreeing. Ships within the US only.

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": {
      "part_id": "<part_id>",
      "name": "<name>",
      "email": "<email>",
      "street": "<street>",
      "city": "<city>",
      "state": "<state>",
      "zip": "<zip>"
    },
    "name": "request_order"
  }
}

Input Schema

NameRequiredDescriptionDefault
zipYesUS ZIP code.
cityYesShipping address: city.
nameYesThe user's full name.
emailYesWhere KinetiCAD sends the confirmed price and delivery date.
notesNoAnything the shop should know: threads, fits, finish, a date the parts are needed by.
phoneNoOptional. The user's phone number.
stateYesUS state, two letters, for example CA.
streetYesShipping address: number and street.
companyNoOptional. The user's company.
part_idYesThe part_id that build_part (or the HTTP upload of a STEP file) returned.
materialNoWhat the part is machined from.aluminum-6061
quantityNoHow many pieces.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • addedInput schema / properties / city / description
      Added value: +"Shipping address: city."
    • addedInput schema / properties / company / description
      Added value: +"Optional. The user's company."
    • addedInput schema / properties / phone / description
      Added value: +"Optional. The user's phone number."
  2. First observed

TDQS

A4.5/5.0
Behavior5/5

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

Annotations only say non-read-only, non-idempotent, open-world, non-destructive. The description adds real behavioral context beyond that: no payment is captured at call time, a named human at KinetiCAD follows up by email within one business day with confirmed price and delivery date, and the user pays only after agreeing. It also discloses a geographic restriction (US shipping only), which is exactly the kind of operational constraint annotations cannot express.

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?

Four short sentences, front-loaded with the action and immediately followed by the precondition. Every sentence carries information (gating, destination of data, payment model, follow-up timing, shipping scope), though 'It sends those details to KinetiCAD' is mildly redundant with the opening sentence.

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 12-parameter, non-idempotent, open-world submission tool with no output schema, the description covers the workflow, payment safety, follow-up timing, and shipping limits well. The remaining gap is that it never hints at what the call returns (an order reference or confirmation) — with no output schema, that leaves the agent unable to set expectations for the user after invoking it.

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 every parameter — including part_id, quantity, material, and the address fields — is already documented in the schema itself. The description only restates that shipping address and email are required, adding no format, constraint, or meaning beyond what the schema provides. Baseline 3 applies when the schema does the heavy lifting.

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 — 'Send an order request for a part to KinetiCAD' — which unambiguously distinguishes it from the sibling build_part, price_part, and view_part tools. An agent knows this is the terminal, outbound ordering step rather than a quoting or building step.

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 gating condition: 'Call this only after the user has seen the price and said yes, and has given a shipping address and an email address.' This states both the when (after a price has been surfaced and accepted) and the when-not (before price acceptance or without address/email), and it implies the correct ordering relative to price_part.

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