Skip to main content
Glama
architectural_modeling_workflow

architectural_modeling_workflow

by Lsc1123

sketchup_import

Imports a workspace asset through SketchUp’s native importer and checks units and editability after import.

Instructions

Import a workspace asset through SketchUp's native importer; inspect units and editability afterwards.

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": {
      "path": "<path>",
      "expected_revision": "<expected_revision>",
      "operation_id": "<operation_id>"
    },
    "name": "sketchup_import"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathYes
asset_idNo
semantic_idNo
expect_solidNo
operation_idYes
expected_revisionYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.1

TDQS

B3/5.0
Behavior3/5

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

Annotations declare the safety profile (mutating, non-idempotent, not destructive, closed-world), so that burden is partly lifted. The description adds genuine value by warning that units and editability may not survive import and must be checked, but it says nothing about why operation_id/expected_revision exist, whether the import can fail destructively, or what authorization it needs.

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 no padding; the mechanism appears before the caveat. It is efficient, though the semicolon-joined second clause could be clearer as a separate instruction.

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?

The output schema exists, so return values need not be explained. But for a six-parameter mutation with three required parameters (including expected_revision and operation_id) and zero schema documentation, the description leaves the agent without enough to invoke 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?

Schema description coverage is 0% across six parameters, so the description must carry the load and does not. It never mentions expect_solid, semantic_id, asset_id, or the concurrency-guard parameters, and 'units'/'editability' are not parameters at all, so they do not illuminate the schema.

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 (import) and resource (workspace asset) plus the mechanism (SketchUp's native importer), so the agent knows what happens. It stops short of distinguishing this from plausible siblings such as sketchup_open or sketchup_restore_opening.

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?

The only guidance is the trailing 'inspect units and editability afterwards', which is a post-condition hint rather than a when-to-use rule. There is no statement about when to prefer this over opening, restoring, or creating geometry directly.

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