Skip to main content
Glama
FullyDefined – AI for SOLIDWORKS

FullyDefined – AI for SOLIDWORKS

activate_sheet

Sets the specified sheet in the active SOLIDWORKS drawing as the working sheet for other drawing tools; returns its size and views and refuses unknown sheet names.

Instructions

Make a sheet of the active drawing the active one, which is the sheet the other drawing tools (set_title_block, add_section_view, add_drawing_dimension and the rest) work on. Returns the sheet's size and views. An unknown name is refused and the active sheet stays as it was.

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

Input Schema

NameRequiredDescriptionDefault
nameYesName of the sheet (see list_drawing_views)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.1/5.0
Behavior4/5

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

With no annotations supplied, the description carries the full burden and does well: it discloses the return payload (sheet size and views), the mutation's scope (only changes the active sheet), and the failure semantics (unknown name is refused and the previous active sheet is preserved — atomic, non-destructive on error). It does not mention preconditions such as requiring an open/active drawing document, which is the main remaining gap.

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?

One compact sentence that front-loads the action, then the consequence, then the return value and error behavior — no filler. The parenthetical enumeration of sibling drawing tools is slightly bulky and could be trimmed to 'the other drawing tools', but it does earn its place by making the dependency concrete.

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?

For a one-parameter selector with no output schema, the description covers what an agent needs: what it changes, what it returns, and what happens on bad input. The only meaningful omission is the precondition that a drawing must be active for the tool to be callable at all.

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?

There is a single parameter with 100% schema description coverage, and the schema already points to list_drawing_views as the source of valid names. The description adds no format, casing, or matching semantics (exact vs partial name) beyond what the schema provides, so the baseline of 3 applies.

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 states a specific verb and resource ('Make a sheet of the active drawing the active one') and immediately clarifies the effect that distinguishes it from siblings: it selects the sheet that set_title_block, add_section_view, add_drawing_dimension and the rest operate on. An agent can tell this apart from add_sheet or list_drawing_views without opening any schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives clear context for when the tool matters: before using the other drawing tools, since they act on whichever sheet is active. It also states the failure condition (unknown name refused, active sheet unchanged). It stops short of explicit when-not guidance or naming list_drawing_views as the way to obtain valid names in the prose, though the schema does that.

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