Skip to main content
Glama
architectural_modeling_workflow

architectural_modeling_workflow

by Lsc1123

sketchup_query

Read-onlyIdempotent

Find SketchUp native instances and identities without dumping all geometry; returns IDs for editing. Use name filters, limits, and offsets for targeted queries.

Instructions

Find native instances and identities without dumping all geometry. Use IDs for editing.

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

Input Schema

NameRequiredDescriptionDefault
idsNo
limitNo
offsetNo
name_containsNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.1

TDQS

C2.9/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 profile is covered. The description adds one genuine behavioral fact beyond them: results are scoped to avoid returning all geometry. It says nothing about pagination behavior, result size, or whether missing IDs error or are skipped.

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 short sentences with no filler, and the scope statement is front-loaded ahead of the workflow hint. Nothing is redundant, though the second sentence is terse to the point of underspecification.

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 exists, so return values need not be described, but the definition still leaves the core object model ("native instances and identities") and three of four parameters undocumented. For a query tool that is the entry point to an edit workflow, that is a meaningful gap.

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 four parameters (ids, limit, offset, name_contains), so the description must compensate and largely does not. "Use IDs" loosely gestures at the ids filter, but limit, offset and name_contains get no mention, leaving an agent to guess filtering and paging semantics.

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 verb "Find" is clear, but the resource is expressed in unexplained jargon ("native instances and identities"), which leaves an agent unsure what entity types are returned. "Without dumping all geometry" hints that this is a lightweight lookup rather than a full model dump, but does not pin down the object model.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

"Use IDs for editing" implies a two-step workflow: query here first, then pass the returned IDs to an editing tool. That is useful implied guidance, but there is no explicit statement of when to prefer this over sketchup_state or drawing_read_slice, and no exclusions.

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