Skip to main content
Glama

KinetiCAD CNC Parts

Price a part

price_part
Read-onlyIdempotent

Get the price to CNC machine a part in the US. KinetiCAD's engine plans how the part is machined (the machine, the setups, the tools and the cycle time), and the price is the setup time and the machine time at a US shop rate, plus the material. Returns the unit price for the quantity, the cost lines, the plan and the delivery date. Planning a new part takes from about 10 seconds to a few minutes: if status is planning, call again after retry_after_seconds. Prices are in US dollars.

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

Input Schema

NameRequiredDescriptionDefault
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. First observed

TDQS

A4.4/5.0
Behavior5/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and non-destructive, so safety is covered. The description adds substantial behavior beyond that: the pricing model (setup + machine time at a US shop rate + material), realistic latency of 10 seconds to a few minutes, the async planning status and retry signal, and the currency. That is exactly the kind of context annotations cannot convey.

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 purpose, then pricing mechanics, then return values, then the polling caveat. Sentences are dense and useful, though the pricing-breakdown explanation is slightly verbose for the decision it supports and could be tightened.

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?

With no output schema, the description compensates by naming what comes back (unit price, cost lines, plan, delivery date). It also covers the async planning behavior an agent must handle, which is the main failure mode for this call. Complete for a read-only pricing tool.

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%, so material, quantity and part_id are already documented with defaults, enum values and ranges. The description adds only mild context — that the returned figure is a unit price for the given quantity — without explaining how material or quantity affect pricing. Baseline 3 is appropriate when the schema carries the parameter burden.

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 (get the price to CNC machine a part) and scopes it geographically and by pricing model. It also implicitly distinguishes itself from build_part by stating that part_id comes from that tool, so an agent can tell what this does versus its siblings.

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?

Gives a clear usage condition for polling ('if status is planning, call again after retry_after_seconds') and prerequisite context (part_id from build_part or a STEP upload). It does not name when to prefer request_order instead, so it stops short of explicit alternatives.

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