Skip to main content
Glama
architectural_modeling_workflow

architectural_modeling_workflow

by Lsc1123

sketchup_create

Creates editable native solids—boxes, prisms, or stairs—from explicit dimensions, with floor Z set as the structural bottom for predictable SketchUp modeling.

Instructions

Create one editable native solid. Floor polygon Z is its structural bottom; choose finished-face conventions explicitly.

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>",
      "shape": "<shape>",
      "expected_revision": "<expected_revision>",
      "operation_id": "<operation_id>"
    },
    "name": "sketchup_create"
  }
}

Input Schema

NameRequiredDescriptionDefault
kindNosolid
nameYes
shapeYes
semantic_idNo
operation_idYes
expected_revisionYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.1

TDQS

C2.8/5.0
Behavior3/5

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

Annotations already declare this is a non-read-only, non-destructive, non-open-world mutation, so the safety profile is covered. The description adds genuinely useful domain context that the flat polygon's Z is the structural bottom, which affects how geometry is placed. It says nothing about how expected_revision or operation_id gate the write, what happens on a stale revision, or whether the creation is recoverable.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two short sentences with no padding and the core action front-loaded, which is structurally sound. The second sentence is compressed to the point of ambiguity: "finished-face conventions" is undefined, so brevity is bought with clarity.

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?

For a 6-parameter mutation with a three-way shape union and 0% schema description coverage, the description is far too thin. An output schema exists so return values need no explanation, but the revision/operation-id contract and the shape-variant selection are still missing.

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 description coverage is 0%, so the description carries the burden and does not meet it. It touches only the Z/floor-plane concept, leaving name, kind, semantic_id, expected_revision, and operation_id — the parameters most likely to cause a failed or wrong call — entirely unexplained.

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 uses a specific verb and resource ("Create one editable native solid"), and the schema's shape union (box/prism/stairs) confirms what a "solid" means. It stops short of distinguishing this from siblings such as sketchup_combine, sketchup_group, or asset_build, so an agent still has to infer which construction tool applies.

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 when-to-use guidance, no mention of prerequisites, and no routing to or away from any alternative. The only usage-adjacent statement, "choose finished-face conventions explicitly," is a caution about conventions rather than a condition for selecting this tool.

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