Skip to main content
Glama

Add Projection Group

add_projection_group

Adds a multi-view projection group of a specified body to a drawing page. Configure standard or custom views for mechanical drawings.

Instructions

Add a multi-view projection group of body to a drawing page. views: list of FreeCAD view codes ('Front', 'Top', 'Right', 'Left', 'Bottom', 'Rear', 'FrontTopLeft', etc.). Default: ['Front', 'Top', 'Right'].

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": {
      "page": "<page>",
      "body": "<body>"
    },
    "name": "add_projection_group"
  }
}

Input Schema

NameRequiredDescriptionDefault
bodyYes
nameNoProjGroup
pageYes
viewsNo
workspaceNoRun this call in this named workspace

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.5.7
    • addedInput schema / properties / workspace
      Added value: +{
      +  "default": "",
      +  "description": "Run this call in this named workspace",
      +  "title": "Workspace",
      +  "type": "string"
      +}
  2. First observed

TDQS

C2.9/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false, and openWorldHint=false, so the mutation/safety profile is covered. The description adds nothing beyond that: no failure modes (missing page, duplicate name), no side effects on page layout, no note that the group is auto-placed.

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?

Two sentences, purpose front-loaded before the parameter detail, with no filler. Minor deductions: the line break mid-sentence is awkward, and the stated default ['Front','Top','Right'] does not match the schema default of null, which could confuse an agent.

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?

For a 5-parameter creation tool with no output schema, the description should say what is returned (e.g., the created group's name/handle for later add_dimension or balloon_drawing calls) and that the page and body must already exist. It covers purpose and the views enum but leaves those operational gaps.

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 coverage is 20% (only `workspace` is described in schema), so the description must compensate. It does add real value for the most complex parameter, enumerating FreeCAD view codes and the fallback view set for `views`, but leaves `page`, `body`, and `name` undocumented in both places.

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?

States a specific verb+resource: adds a multi-view projection group of a named `body` onto a drawing page. An agent can distinguish this from siblings like add_section_view or render_view by the 'projection group' framing. It stops short of explicitly contrasting with those siblings, so it is clear but not sibling-differentiated.

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 statement of when to use this versus add_section_view, render_view, or add_thumbnail, and no prerequisites (an existing drawing page, a body in the active document, workspace context). The drawing context is only implied by 'to a drawing page'.

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

Deploy Server

Other Tools