Skip to main content
Glama
BIM Viewer MCP Server

BIM Viewer MCP Server

Reset view

reset
Read-onlyIdempotent

Restores the viewer to a clean whole-building overview by clearing element highlights, room volumes, and camera focus; safe and idempotent to call at any time.

Instructions

Reset the viewer to a clean state showing the whole building.

Clears any element highlights, room volumes, and camera focus. Safe to call at any time; idempotent.

Returns: {"applied": bool}.

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": "reset"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/5.0
Behavior3/5

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

The description usefully discloses what state is discarded (highlights, room volumes, camera focus), which is more than the annotations convey. However, 'safe to call at any time; idempotent' restates idempotentHint and destructiveHint=false rather than adding new behavioral context, so the net addition is modest against an already rich annotation set.

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 the core behavior front-loaded, followed by a returns block. The 'Returns' note duplicates the existing output schema and the idempotency claim partially duplicates annotations, but neither is costly.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no parameters, a declared output schema, and full annotation coverage, the description supplies everything an agent needs: the effect, the scope, and the safety profile. Nothing essential is missing for a zero-argument reset action.

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 there is nothing for the description to disambiguate; baseline 4 applies. No misleading parameter language is present.

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 and resource ('Reset the viewer') plus the resulting scope ('clean state showing the whole building'), then enumerates exactly what is undone: highlights, room volumes, camera focus. This functionally separates it from highlight_elements, isolate, and zoom_to without naming them, though it never explicitly contrasts with those siblings.

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?

The phrase 'Safe to call at any time' gives a permissive usage signal, but there is no guidance on when an agent should prefer reset over isolate or zoom_to for returning to a full-building view. Usage is implied rather than directed.

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