Skip to main content
Glama
architectural_modeling_workflow

architectural_modeling_workflow

by Lsc1123

sketchup_export

Destructive

Exports actual world geometry, native face rings, UVs, materials, instance paths, and scenes to JSON for downstream architectural modeling and validation.

Instructions

Export actual world geometry, native face rings, UV, materials, instance paths and scenes.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "sketchup_export"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathNo.amw/geometry/current.json

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.1

TDQS

C2.7/5.0
Behavior2/5

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

Annotations already declare destructiveHint=true and readOnlyHint=false, but the description never explains that consequence: it does not say a file is written, that an existing file at the path may be overwritten, or anything about output size or failure modes. The only added context is the scope of exported content (face rings, UVs, instance paths), which is useful but does not address the destructive behavior the annotations flag.

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 front-loaded sentence with a compact enumeration and no filler. Sizing is appropriate; it simply omits information rather than wasting words.

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?

An output schema covers the return shape, which helps. But for a destructive file-writing tool with one undocumented parameter, the description leaves out where the output goes, whether existing data is overwritten, and how it differs from the other export tools — gaps an agent needs closed before invoking it.

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?

There is a single parameter, path, with 0% schema description coverage and a default of '.amw/geometry/current.json'. The description never mentions the path argument, its default, or the file format written, so it adds nothing to a completely undocumented parameter.

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 ('Export') followed by an enumerated payload: world geometry, native face rings, UVs, materials, instance paths, and scenes. That enumeration tells an agent exactly what data is captured, which is more specific than most siblings. It stops short of differentiating itself from handoff_export or sketchup_capture, so it is not a 5.

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 at all — no mention of when this export is preferable to handoff_export or sketchup_capture, and no prerequisite context. The agent must infer the use case entirely from the verb.

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