Skip to main content
Glama
Sign In
Model MCP

Model MCP

by sharafutdinovdi
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Local

Isolate Elements

revit_isolate
Read-onlyIdempotent

Temporarily isolates specified Revit element IDs in the active view and resets the view when given an empty list.

Instructions

Temporarily isolate element IDs in the active view; an empty list resets.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "element_ids": "<element_ids>"
    },
    "name": "revit_isolate"
  }
}

Input Schema

NameRequiredDescriptionDefault
resetNo
documentNoTitle or file name substring of the target open document; needed when several are open.
element_idsYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed6 schema fields changedv0.10.0
    • changedInput schema / properties / document / description
      Previous value: -"Case-insensitive substring of the target open document's title or file name. Required to disambiguate when the Revit process has more than one document open; omit only when a single document is open (the active document is used). An unknown or ambiguous reference is rejected before any change."New value: +"Title or file name substring of the target open document; needed when several are open."
    • removedInput schema / properties / document / title
      Removed value: -"Document"
    • removedInput schema / properties / element_ids / title
      Removed value: -"Element Ids"
    • removedInput schema / properties / reset / title
      Removed value: -"Reset"
    • removedInput schema / title
      Removed value: -"revit_isolateArguments"
    • removedOutput schema / title
      Removed value: -"revit_isolateDictOutput"
  2. Addedv0.7.0

TDQS

A3.5/5.0
Behavior3/5

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

The annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is covered. The description adds useful context by saying isolation is temporary and that an empty list restores the normal view state, but it doesn't resolve how the separate reset boolean differs from that empty-list behavior.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is one tight sentence with the core action and scope up front and the reset behavior appended, with no wasted words.

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

Completeness3/5

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

An output schema exists and annotations cover safety, so the bar is moderate. Still, the ambiguity between the reset parameter and the empty element_ids list leaves a calling agent without full confidence in how to restore the view.

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

Parameters3/5

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

Schema coverage is only 33%, and the description explains element_ids behavior (an empty array resets) but says nothing about the reset boolean, which is undocumented in the schema and overlaps in purpose with the empty-list reset. The document parameter is described in the schema, not the description.

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 has a specific verb and resource ("Temporarily isolate element IDs in the active view") and even notes the effect of an empty list. It doesn't distinguish itself from related siblings like revit_set_view_visibility or revit_select, which also control what is visible or selected.

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?

"Temporarily isolate" plus "an empty list resets" implies when to use it, but there is no explicit contrast with revit_set_view_visibility or revit_select, and no statement about prerequisites. A reader must infer that isolation is a view-state operation that does not change the model.

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

Deploy Server

Other Tools