Skip to main content
Glama

Revit MCP

by io.scanbimlabs

revit_get_parameters

When to use: Enumerate the Revit parameters (type + instance) that appear on elements in a given category, or on one specific element by objectid. Returns unique values per parameter and how many elements carry it — ideal for schema discovery before building a schedule. When NOT to use: Do not use when you just need the elements themselves (use revit_get_elements), or to modify values — this is read-only. APS scopes: data:read viewables:read (Model Derivative metadata + properties). Rate limits: APS default ~50 req/min per app per endpoint; Model Derivative translation jobs ~60 req/min; OSS uploads size-limited per file to 100MB for direct upload, larger via resumable. Errors: 401 APS token expired — refresh. 403 scope insufficient — add viewables:read. 404 URN not found — verify model_id. 429 rate limited — back off. 5xx APS upstream — retry with jitter. Side effects: Read-only. Idempotent.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
categoryYesRevit category to filter on (case-insensitive substring match). Ignored when element_id is supplied.
model_idYesBase64url-encoded URN of the translated Revit model (returned from revit_upload). Always begins with 'dXJu'.
element_idNoOptional APS Model Derivative objectid of a single element to inspect. When provided, overrides category filtering and returns parameters only for that element.

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed7 schema fields changed
    • changedInput schema / properties / category / description
      Previous value: -"Revit category to filter"New value: +"Revit category to filter on (case-insensitive substring match). Ignored when element_id is supplied."
    • addedInput schema / properties / category / examples
      Added value: +[
+  "Doors"
+]
    • changedInput schema / properties / element_id / description
      Previous value: -"Optional specific element objectid to query"New value: +"Optional APS Model Derivative objectid of a single element to inspect. When provided, overrides category filtering and returns parameters only for that element."
    • addedInput schema / properties / element_id / examples
      Added value: +[
+  "12345"
+]
    • changedInput schema / properties / model_id / description
      Previous value: -"Base64-encoded URN"New value: +"Base64url-encoded URN of the translated Revit model (returned from revit_upload). Always begins with 'dXJu'."
    • addedInput schema / properties / model_id / examples
      Added value: +[
+  "dXJuOmFkc2sub2JqZWN0czpvcy5vYmplY3Q6c2NhbmJpbS1yZXZpdC0xNzMxMjM0NTY3L015QnVpbGRpbmcucnZ0"
+]
    • addedInput schema / properties / model_id / pattern
      Added value: +"^dXJu[A-Za-z0-9_-]+$"
  2. First observed

TDQS

A4.6/5.0
Behavior5/5

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

With no annotations, the description carries full burden and discloses read-only nature, idempotency, APS scopes, rate limits, and error codes. This goes beyond basic expectations and sets clear expectations for behavior and side effects.

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?

The description is organized with labeled sections and front-loaded with the core purpose. While it includes lengthy rate limit and error details, these are structured and relevant, though slightly verbose. Each sentence earns its place in the context of a no-annotation tool.

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?

The description covers purpose, use cases, return values, side effects, scopes, rate limits, and errors. For a tool with no output schema, it fully explains what to expect and how to handle failures, making it contextually complete.

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 input schema already provides 100% coverage with detailed descriptions of each parameter, including how category is ignored when element_id is supplied. The description adds no new parameter semantics beyond the schema, so the baseline score of 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool enumerates Revit parameters (type + instance) for a category or single element, and returns unique values with element counts. It distinguishes itself from revit_get_elements which returns elements themselves, making the purpose unambiguous.

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

Usage Guidelines5/5

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

Explicit 'When to use' and 'When NOT to use' sections specify the ideal use case (schema discovery for schedules) and explicitly point to revit_get_elements for element retrieval. This provides clear guidance on alternatives and exclusions.

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

All Revit MCP toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.5/5.0
Disambiguation5/5

Each tool has a clearly distinct purpose: upload ingests, get_elements/get_parameters/get_sheets/get_views retrieve different types of data, run_schedule queries tabular views, clash_detect performs spatial analysis, and export_ifc converts formats. No two tools overlap in function; even get_sheets and get_views are explicitly differentiated in their descriptions.

Naming Consistency5/5

All tools follow a consistent revit_<verb> pattern in snake_case, with get_* for read operations and action verbs for other operations. The naming is predictable and uniform across the entire set.

Tool Count5/5

Eight tools is well within the ideal 3-15 range and appropriately matches the server's scope of Revit model ingestion, exploration, analysis, and export. Each tool earns its place without redundancy or bloat.

Completeness3/5

The tool set covers the core lifecycle (upload, read elements/parameters/sheets/views, run schedules, clash detect, export IFC), but there is no tool to check translation status or poll the manifest, which is referenced in descriptions but not provided. This is a notable gap that can cause agents to call read tools before translation completes, leading to failures.

Resources