Skip to main content
Glama

Protogen CAD

Export cad design

export_cad_design
Read-onlyIdempotent

Export a CAD design as OpenSCAD, STEP contract metadata, or manufacturing brief.

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": {
      "design_id": "<design_id>"
    },
    "name": "export_cad_design"
  }
}

Input Schema

NameRequiredDescriptionDefault
design_idYesThe design id returned by generate_cad_design.
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.
export_formatNoopenscad (default), step_contract or manufacturing_brief.openscad

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • addedInput schema / properties / design_id / description
      Added value: +"The design id returned by generate_cad_design."
    • addedInput schema / properties / export_format / description
      Added value: +"openscad (default), step_contract or manufacturing_brief."
    • 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."
  2. Changed1 schema field changed
    • addedInput schema / properties / payment_ref
      Added value: +{
      +  "anyOf": [
      +    {
      +      "type": "string"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ],
      +  "default": null,
      +  "title": "Payment Ref"
      +}
  3. First observed

TDQS

B3.2/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and closed-world scope, so the safety profile is covered. The description adds nothing beyond the annotations: it does not mention credit consumption implied by payment_ref, whether repeated exports are cached, or any side effects, and the format list merely restates the schema enum values.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single front-loaded sentence with zero filler; every clause (verb, resource, the three formats) carries information. Nothing could be removed without losing content.

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?

An output schema exists, so return values need not be explained, and annotations plus full schema coverage handle safety and parameters. The remaining gap is that the description never states the preconditions or the free-tier/paid-credit behavior that the payment_ref parameter hints at, but overall it is sufficient to call the tool correctly.

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% and all three parameters carry their own descriptions, including the format values and the payment_ref tiering rule. The description adds no meaning beyond what the schema already states, so the baseline 3 applies.

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?

The description gives a specific verb (export) and resource (CAD design) and enumerates the three concrete output artifacts, so an agent knows exactly what it produces. It stops short of differentiating itself from siblings such as generate_cad_design or manufacturing_plan_from_spec, which is what would push this to a 5.

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?

There is no explicit when-to-use guidance, no statement of prerequisites (e.g. that a design must exist from generate_cad_design), and no named alternatives or exclusions. Usage is only weakly implied by the word 'export'.

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.