Retrieve the active SketchUp model's session ID, file path, units, edit context, and runtime capabilities to inspect its current state and available operations.
Get model session ID, path, units, edit context and runtime capabilities.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Changes observed during successful MCP inspections.
v1.3.1Input schema / additionalPropertiesAdded value: +falsev1.0.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint, idempotentHint, non-destructive, and closed-world, so safety behavior is covered. The description adds content-level detail (what context is retrievable) but says nothing about return format, whether session ID is stable, or how 'edit context' behaves — acceptable given the annotation coverage.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
A single front-loaded sentence with no filler; the returned field list is packed efficiently and every word earns its place.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
With no output schema, the description carries the burden of explaining returns, and it enumerates the five categories of data delivered. For a zero-param read-only info tool this is largely sufficient, with only minor gaps around format and stability of the returned values.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Zero parameters, so the schema imposes no semantic burden on the description; the baseline of 4 applies. The description does not need to explain any argument meaning.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
States a specific verb ('Get') and resource ('model'), then enumerates the concrete data returned: session ID, path, units, edit context, runtime capabilities. That distinguishes it reasonably from siblings like model_stats or bridge_status, though it never names them or explicitly contrasts.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
No explicit when-to-use or when-not-to-use guidance, and no alternatives are named. Usage is only implied: an agent infers this is the orientation call for retrieving model/environment context before other operations.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.