Skip to main content
Glama
cad2revit-mcp

cad2revit-mcp

export_report

Generates a modeling report for a CAD-to-Revit conversion task, covering inspection results, auto-completion rates, topology, failure details, and items requiring review.

Instructions

导出建模报告,含体检结论、自动完成比例、图关系与拓扑、失败明细与待复核清单。

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": {
      "task_id": "<task_id>"
    },
    "name": "export_report"
  }
}

Input Schema

NameRequiredDescriptionDefault
formatNomarkdown
task_idYes
templateNodefault

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.1

TDQS

C2.8/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full behavioral burden. It discloses only the report's payload; it does not say whether a file is written to disk or content is returned, where it goes, whether the operation is idempotent, what permissions or prior state it needs, or how expensive it is. For an export/mutation-style tool this is a substantive gap.

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?

A single front-loaded sentence starting with the verb, with the payload enumerated compactly. Every clause contributes information; no redundant restatement of the tool name.

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, so return values need not be explained, and the described report sections give a good picture of the result. However, with zero parameter documentation and zero annotations, an agent still lacks what it needs to choose format/template or predict side effects.

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% across three parameters (task_id, format, template), and the description adds no meaning for any of them — it never mentions task scoping, output format, or what a template changes. The content enumeration hints at what format/template control, but no explicit mapping is given.

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 concrete verb+resource (export a modeling report) and enumerates the report's contents (inspection conclusions, auto-completion ratio, graph relationships/topology, failure details, pending-review list). An agent can tell this is a report-generation tool, distinct from siblings like query_graph or check_model, though the description never explicitly contrasts them.

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 instead of check_model or query_graph, no prerequisites (e.g., must a task_id exist / must analysis have run first), and no statement of when not to use it. The agent must infer that this is the terminal 'produce output' step.

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