viridis-agent-fleet

Overview Schema Source Related Servers Discussions Admin

protogen__manufacturing_plan_from_spec

Convert a product spec into a manufacturing plan with bill of materials, DFM notes, and cost estimate.

Instructions

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

Input Schema

Name	Required	Description	Default
`payment_ref`	No
`product_spec`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed7 schema fields changedv0.1.11Jul 18, 2026
- 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 / properties / product_spec / additionalProperties
```
Added value: +true
```
- addedInput schema / properties / product_spec / title
```
Added value: +"Product Spec"
```
- addedInput schema / title
```
Added value: +"manufacturing_plan_from_specArguments"
```
Changed4 schema fields changedv0.1.9Jul 16, 2026
- addedInput schema / properties / payment_ref
```
Added value: +{
+  "type": "string"
+}
```
- removedInput schema / properties / product_spec / additionalProperties
```
Removed value: -true
```
- removedInput schema / properties / product_spec / title
```
Removed value: -"Product Spec"
```
- removedInput schema / title
```
Removed value: -"manufacturing_plan_from_specArguments"
```
Changed3 schema fields changedJul 13, 2026
- addedInput schema / properties / product_spec / additionalProperties
```
Added value: +true
```
- addedInput schema / properties / product_spec / title
```
Added value: +"Product Spec"
```
- addedInput schema / title
```
Added value: +"manufacturing_plan_from_specArguments"
```
Changed3 schema fields changedJul 13, 2026
- removedInput schema / properties / product_spec / additionalProperties
```
Removed value: -true
```
- removedInput schema / properties / product_spec / title
```
Removed value: -"Product Spec"
```
- removedInput schema / title
```
Removed value: -"manufacturing_plan_from_specArguments"
```
First observedJul 13, 2026

TDQS

C2.9/5.0

Behavior2/5

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

No annotations exist, so description must fully disclose behavior. It mentions generating outputs but lacks details on side effects, permissions, rate limits, or what happens to input data. The tool likely performs computation without persistent changes, but no explicit statement.

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?

Single sentence efficiently conveys core purpose. The prefix adds context but is not essential. Concise but lacks sufficient detail for the task complexity.

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?

With no output schema and 2 parameters, description is too sparse. Missing return value format, error handling, expected structure of product_spec, and any constraints. Incomplete for an agent to reliably invoke.

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

Parameters2/5

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

Schema coverage is 0%. Description only hints at 'product_spec' indirectly but provides no structure or format details. 'payment_ref' parameter is completely ignored. Does not add meaningful semantics beyond parameter names.

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?

Description clearly states the tool generates a manufacturing plan, BOM, DFM notes, and cost estimate from a product spec. It distinguishes from siblings like protogen__generate_cad_design by specifying the output type (manufacturing plan vs CAD design) and input (product spec).

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?

No guidance on when to use this tool versus alternatives like protogen__generate_cad_design. No prerequisites, exclusions, or context provided. The description simply states what it does without usage context.

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

Deploy Server