Skip to main content
Glama

Protogen CAD

Manufacturing plan from spec

manufacturing_plan_from_spec

Generate a manufacturing plan, BOM, DFM notes, and cost estimate from a product spec.

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": {
      "product_spec": "<product_spec>"
    },
    "name": "manufacturing_plan_from_spec"
  }
}

Input Schema

NameRequiredDescriptionDefault
request_idNoOptional. Your id for this call. Repeat it to retry safely: the same request_id is never charged twice.
payment_refNoOptional. A paid credit or payment reference, used only after the free daily calls. Leave it out to use the free tier or a seat.
product_specYesThe product specification, as an object.

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • addedInput schema / properties / payment_ref / description
      Added value: +"Optional. A paid credit or payment reference, used only after the free daily calls. Leave it out to use the free tier or a seat."
    • addedInput schema / properties / product_spec / description
      Added value: +"The product specification, as an object."
    • addedInput schema / properties / request_id / description
      Added value: +"Optional. Your id for this call. Repeat it to retry safely: the same request_id is never charged twice."
  2. Changed2 schema fields changed
    • addedInput schema / properties / payment_ref
      Added value: +{
      +  "anyOf": [
      +    {
      +      "type": "string"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ],
      +  "default": null,
      +  "title": "Payment Ref"
      +}
    • addedInput schema / properties / request_id
      Added value: +{
      +  "anyOf": [
      +    {
      +      "type": "string"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ],
      +  "default": null,
      +  "title": "Request Id"
      +}
  3. First observed

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false, idempotentHint=false and openWorldHint=false, so the mutation/safety profile is covered. The description adds that the call yields a composite bundle of artifacts (plan, BOM, DFM notes, cost estimate), which hints at a substantive generative operation, but says nothing about billing/credit consumption, latency, or what happens on partial failure.

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?

One sentence with zero filler, front-loaded with the verb and the deliverables. It is arguably too terse for a multi-artifact generative tool, but nothing is redundant.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

An output schema exists, so return values need no explanation, and annotations plus full schema coverage carry the structured burden. The remaining gap is the nested, additionalProperties-enabled product_spec object: the description gives no hint about required content or minimum viable spec, which is the main source of misuse risk.

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 description coverage is 100%, so baseline is 3; request_id and payment_ref are fully documented in the schema (retry safety, free tier). The description adds only that "product_spec" drives generation, without indicating what fields the free-form object should contain.

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?

A specific verb ("Generate") with a concrete resource ("manufacturing plan, BOM, DFM notes, and cost estimate") and an explicit input ("from a product spec"). An agent can tell this produces downstream manufacturing artifacts rather than CAD geometry, distinguishing it in spirit from generate_cad_design/export_cad_design, though it never names an alternative.

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

Usage Guidelines2/5

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

States the input prerequisite (a product spec) but gives no when-to-use or when-not-to-use guidance relative to siblings like generate_cad_design or export_cad_design. An agent must infer that this is the post-design manufacturing-analysis step rather than the design step.

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.