Skip to main content
Glama
cad2revit-mcp

cad2revit-mcp

query_graph

Query the building element relationship graph by element ID, relation type, and neighbor depth to retrieve nodes, relations, anomalies, and a readable summary for BIM model verification.

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

Input Schema

NameRequiredDescriptionDefault
depthNo
task_idYes
element_idNo
relation_typesNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.1

TDQS

B3.2/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full behavioral burden. It does disclose the output shape (nodes, relations, anomalies, readable summary), which is useful, but it says nothing about what prerequisites exist, what 'anomalies' means, or whether the query is read-only or side-effect free. For a query tool the risk profile is low, but the disclosure remains thin.

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 sentence front-loads the query scope and then the return payload, with no wasted clauses. It is appropriately sized for the amount of information conveyed. Only the total absence of supporting guidance keeps it from being a model of compactness.

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 the description needn't explain return values in depth, and it does summarize them anyway. However, for a four-parameter graph query with an unexplained required task_id and no usage framing against seven siblings, the definition leaves real gaps an agent would need to close by trial.

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 description coverage is 0%, so the description must compensate for all four parameters. It maps onto three of them — element, relation type, and neighborhood depth — but only by restating their names, adding no format, allowed values, or default behavior. It never mentions task_id at all, despite that being the sole required parameter.

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: query the element relationship graph, scoped by element, relation type, and neighborhood depth, and it also enumerates the return payload (nodes, relations, anomalies, summary). That is far more informative than the bare name 'query_graph'. It never names a sibling to contrast with (check_model, detect_components, parse_dwg), so the agent must infer the boundary itself.

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?

There is no when-to-use or when-not-to-use guidance, and no mention of the alternatives in the sibling set. The only usage signal is implicit in the verb 'query', which suggests a read operation over an existing graph rather than a build or validation step. An agent has to guess at the boundary with check_model or detect_components.

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