Skip to main content
Glama

Close Sketch

close_sketch
Read-only

Recomputes a sketch's degrees-of-freedom status and reports geometry count, constraint count, open vertices, and whether it is fully constrained.

Instructions

Recompute and report DOF status. Returns {geometry_count, constraint_count, open_vertices, fully_constrained}.

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

Input Schema

NameRequiredDescriptionDefault
sketchYes
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.8/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, and the description is consistent with that by framing the call as 'recompute and report'. It also usefully lists the return payload in the absence of an output schema. What remains unexplained is the 'close' semantics: whether sketch editing state changes, whether the sketch stays open, or whether anything downstream is affected.

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 tight sentences with the operation front-loaded and the return shape packed into a compact literal. No filler, though the brevity contributes to the gaps elsewhere rather than being purely a virtue.

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?

Including the return fields is valuable given there is no output schema, and annotations cover the safety profile. But for a two-parameter tool whose primary parameter is undocumented, and with the name/behavior ambiguity unresolved, it falls short of fully equipping an agent to call it correctly.

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?

Only the optional 'workspace' parameter is documented in the schema (50% coverage); 'sketch' has no description at all. The description does not say whether 'sketch' is a handle, name, or ID, nor that 'workspace' is optional and defaults to the active workspace, so it does not compensate for the coverage gap.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a concrete operation ('Recompute and report DOF status') and enumerates the returned fields, which is more than a restatement of the name. However, it never reconciles the name 'close_sketch' with the read-only recompute behavior, so an agent cannot tell whether this finalizes/exits a sketch or just measures it. No sibling differentiation against add_sketch_constraint or verify_feature.

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 guidance on when to call this versus related tools such as add_sketch_constraint, check_shape, or verify_feature. Nothing states whether it should be called after adding constraints or before padding, nor any precondition like an open sketch.

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