Skip to main content
Glama
Sign In
Model MCP

Model MCP

by sharafutdinovdi
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Local

Batch collection status

revit_batch_status
Read-onlyIdempotent

Read durable batch run and model status after the initiating client exits, so you can check Revit processing results without an active session.

Instructions

Read durable run and model status after the initiating client exits.

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": {
      "run_id": "<run_id>"
    },
    "name": "revit_batch_status"
  }
}

Input Schema

NameRequiredDescriptionDefault
run_idYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv0.10.0
    • removedInput schema / properties / run_id / title
      Removed value: -"Run Id"
    • removedInput schema / title
      Removed value: -"revit_batch_statusArguments"
    • removedOutput schema / title
      Removed value: -"revit_batch_statusDictOutput"
  2. Addedv0.7.0

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so the safety profile is covered. The description adds useful behavioral context by stating the status is durable and remains readable after the initiating client exits. It does not add further detail about what "run status" or "model status" includes, though the output schema may cover return values.

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 a single, front-loaded sentence with no wasted wording. It clearly leads with the action and resource before adding the timing condition.

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?

The tool has annotations, an output schema, and only one parameter, which lowers the description burden. Still, for a batch-status tool the description should ideally clarify how run_id is obtained and how this differs from revit_batch_fetch or revit_jobs. It is minimally adequate but leaves those routing and parameter-origin gaps.

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

Parameters2/5

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

Schema description coverage is 0% and the single required parameter run_id is undocumented in the schema. The description does not mention run_id at all, nor does it explain where to obtain it (for example, from revit_batch_start). With low schema coverage, this is a clear gap.

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 states a specific verb and resource: "Read durable run and model status." It is more specific than the tool name alone and distinguishes itself from batch actions like start/cancel by focusing on status. It does not explicitly name the sibling alternatives such as revit_batch_fetch or revit_jobs, so it falls short of a 5.

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 "after the initiating client exits" gives a clear timing/context signal for when to use the tool. However, it does not explicitly say when to use this instead of revit_batch_fetch, revit_jobs, or other status-like siblings, nor does it provide exclusions.

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