Skip to main content
Glama
Sign In
Revit MCP

Revit MCP

by mcp-servers-for-revit
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

get_selected_elements

Retrieve currently selected elements in Revit with optional limit control for focused data extraction.

Instructions

Get elements currently selected in Revit. You can limit the number of returned elements.

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

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum number of elements to return

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full burden. It discloses the ability to limit the number of returned elements, which is useful. However, it doesn't mention edge cases like empty selection or default behavior, but for a simple getter this is acceptable.

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?

Two short sentences, no unnecessary words. Front-loaded with the core purpose, then describes the limit parameter.

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?

Given the low complexity (one optional parameter, no output schema, no annotations), the description is reasonably complete. It covers the core function and the limit option, though it could mention return format or behavior when nothing is selected.

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?

The schema already provides a description for the 'limit' parameter, so coverage is 100%. The description merely repeats this information ('You can limit the number of returned elements') without adding new meaning.

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 clearly states the tool gets elements currently selected in Revit. This distinguishes it from sibling tools like get_current_view_elements, though it doesn't explicitly name alternatives.

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?

No guidance on when to use this tool versus alternatives. The description implies use when you need selected elements but doesn't compare with get_current_view_elements or other sibling tools.

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