viridis-agent-fleet

Overview Schema Source Related Servers Discussions Admin

protogen__export_cad_design

Export CAD designs as OpenSCAD, STEP contract metadata, or manufacturing brief by providing a design ID and optional payment reference.

Instructions

[protogen — MCP CAD services (measure -> CAD)] 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": "protogen__export_cad_design"
  }
}

Input Schema

Name	Required	Default
`design_id`	Yes
`payment_ref`	No
`export_format`	No	openscad

Schema Changelog

Changes observed during successful MCP inspections.

Changed7 schema fields changedv0.1.11Jul 18, 2026
- addedInput schema / properties / design_id / title
```
Added value: +"Design Id"
```
- addedInput schema / properties / export_format / title
```
Added value: +"Export Format"
```
- addedInput schema / properties / payment_ref / anyOf
```
Added value: +[
+  {
+    "type": "string"
+  },
+  {
+    "type": "null"
+  }
+]
```
- addedInput schema / properties / payment_ref / default
```
Added value: +null
```
- addedInput schema / properties / payment_ref / title
```
Added value: +"Payment Ref"
```
- removedInput schema / properties / payment_ref / type
```
Removed value: -"string"
```
- addedInput schema / title
```
Added value: +"export_cad_designArguments"
```
Changed4 schema fields changedv0.1.9Jul 16, 2026
- removedInput schema / properties / design_id / title
```
Removed value: -"Design Id"
```
- removedInput schema / properties / export_format / title
```
Removed value: -"Export Format"
```
- addedInput schema / properties / payment_ref
```
Added value: +{
+  "type": "string"
+}
```
- removedInput schema / title
```
Removed value: -"export_cad_designArguments"
```
Changed3 schema fields changedJul 13, 2026
- addedInput schema / properties / design_id / title
```
Added value: +"Design Id"
```
- addedInput schema / properties / export_format / title
```
Added value: +"Export Format"
```
- addedInput schema / title
```
Added value: +"export_cad_designArguments"
```
Changed3 schema fields changedJul 13, 2026
- removedInput schema / properties / design_id / title
```
Removed value: -"Design Id"
```
- removedInput schema / properties / export_format / title
```
Removed value: -"Export Format"
```
- removedInput schema / title
```
Removed value: -"export_cad_designArguments"
```
First observedJul 13, 2026

TDQS

C2.8/5.0

Behavior2/5

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

With no annotations provided, the description carries the full burden. It labels the tool as 'Export' which suggests a read operation, but does not disclose side effects, security requirements, or what happens with the output. The payment_ref parameter hints at financial implications but remains unexplained.

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?

The description is a single sentence that efficiently names the action and outputs. However, it could be improved by structuring information about parameters and usage into discrete sentences.

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

Completeness2/5

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

Without output schema or detailed parameter explanations, the description is insufficient for an agent to confidently invoke the tool. The return format (e.g., file download, URL) is not mentioned, and payment requirements are opaque.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Scheama description coverage is 0%, yet the description does not explain any of the three parameters (design_id, payment_ref, export_format). The export formats listed do not map to acceptable values for export_format, leaving the agent without critical input guidance.

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?

The description clearly states the tool exports a CAD design and lists three specific export formats (OpenSCAD, STEP contract metadata, manufacturing brief). This differentiates from sibling tools like protogen__generate_cad_design which creates designs rather than exporting them.

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?

The description provides no guidance on when to choose each export format, nor conditions for using this tool over alternatives. It does not mention prerequisites like payment that might be implied by the payment_ref parameter.

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

Deploy Server