Skip to main content
Glama
architectural_modeling_workflow

architectural_modeling_workflow

by Lsc1123

sketchup_state

Read-onlyIdempotent

Inspect document identity, unsaved changes, disk drift, scene, and live revision to confirm the true state of a SketchUp project before modeling or saving.

Instructions

Inspect actual document identity, unsaved changes, disk drift, scene and live revision.

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_state"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.1

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=false, so the safety and side-effect profile is fully covered by structured fields. The description adds useful behavioral content beyond that by naming the specific signals it surfaces (unsaved changes, disk drift, live revision), which implies it reconciles in-memory state against disk. It does not disclose cost, latency, or whether inspection triggers any document refresh, so it is additive but not rich.

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 filler, and the action verb leads. It is slightly telegraphic—the noun list reads as compressed jargon ("disk drift," "live revision")—but every phrase carries meaning and nothing is wasted.

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 zero-parameter, read-only inspection tool with full annotation coverage and an output schema, the description supplies enough for an agent to select and call it correctly. Return-value structure is handled by the output schema, so no gap exists there. The only omission is explicit routing guidance relative to siblings, which is a minor shortfall at this complexity level.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool takes zero parameters, so the schema imposes no semantic burden and the baseline for this dimension applies. The description correctly devotes no space to parameter explanation, focusing entirely on what the inspection returns.

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 pairs a specific verb ("Inspect") with a concrete resource (the SketchUp document's state) and enumerates the facets returned: document identity, unsaved changes, disk drift, scene, and live revision. That makes it clearly a read-only status probe, distinguishable from siblings like sketchup_save, sketchup_open, or sketchup_query. It stops short of a single crisp one-line statement of intent, but the resource and scope are unambiguous.

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 explicit guidance on when to call this versus alternatives such as sketchup_query or sketchup_open, and no stated preconditions. An agent can infer it belongs in a pre-save/pre-edit verification step, but that inference is left entirely to the reader. No when-not-to-use case is given.

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