Skip to main content
Glama

Protogen CAD

Create cad workspace

create_cad_workspace

Create a ProtoGen CAD workspace for another agent or workflow.

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": {
      "project_name": "<project_name>",
      "owner_agent": "<owner_agent>",
      "design_goal": "<design_goal>"
    },
    "name": "create_cad_workspace"
  }
}

Input Schema

NameRequiredDescriptionDefault
request_idNoOptional. Your id for this call. Repeat it to retry safely: the same request_id is never charged twice.
constraintsNoOptional. Design constraints, for example size limits or loads.
design_goalYesWhat the design must achieve, in plain words.
owner_agentYesId of the agent or workflow that owns the workspace.
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.
project_nameYesName for the CAD workspace.

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed6 schema fields changed
    • addedInput schema / properties / constraints / description
      Added value: +"Optional. Design constraints, for example size limits or loads."
    • addedInput schema / properties / design_goal / description
      Added value: +"What the design must achieve, in plain words."
    • addedInput schema / properties / owner_agent / description
      Added value: +"Id of the agent or workflow that owns the workspace."
    • 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 / project_name / description
      Added value: +"Name for the CAD workspace."
    • 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 safety profile is covered. The description adds only the ownership/delegation nuance; it says nothing about billing/credit consumption or what state is created, both of which matter for a non-idempotent create. Adequate but thin.

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?

A single front-loaded sentence with zero filler and the resource named immediately. It is efficient, though the brevity borders on under-specification rather than crispness.

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 not be explained, and all parameters are documented in the schema. However, for a non-idempotent create with a paid-credit path, the description omits any mention of cost, quota interaction, or what the resulting workspace state is, leaving the agent to piece that together from the schema.

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%, including detailed notes on request_id retry semantics and payment_ref credit usage, so the schema carries the parameter burden. The description contributes no additional meaning about any of the six parameters, which is the baseline expectation when coverage is complete.

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 states a specific verb and resource ("Create a ProtoGen CAD workspace") and adds a scope qualifier ("for another agent or workflow"), which separates it from siblings like generate_cad_design and export_cad_design. It does not explicitly name or differentiate against those siblings, keeping it just below 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 and no alternatives are named; the agent must infer that this provisions a workspace before generate_cad_design is called. The phrase "for another agent or workflow" hints at a delegation scenario but never states prerequisites or exclusions.

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.