Skip to main content
Glama
cad2revit-mcp

cad2revit-mcp

resolve_ambiguities

Adopt, correct, or exclude low-confidence or topologically anomalous CAD components, then record the rationale for each decision.

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>",
      "decisions": "<decisions>"
    },
    "name": "resolve_ambiguities"
  }
}

Input Schema

NameRequiredDescriptionDefault
task_idYes
decisionsYes
apply_to_similarNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.1

TDQS

B3.1/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 disclosure burden. It usefully reveals that this is a mutating adjudication tool with three decision modes and that it persists a rationale record. It says nothing about reversibility, permissions, conflict handling, or the cascading effect of applying a decision to similar components, which is a meaningful gap for a write tool with zero annotation coverage.

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 that states the operation, the target, and the recorded output with no filler. It is efficient, though its brevity is partly the cause of the parameter and behavioral gaps rather than a virtue in itself.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The presence of an output schema excuses it from describing return values, but for a three-parameter mutation tool with no annotations and no schema descriptions, the definition is too thin. The batch/propagation behavior of apply_to_similar and the identity semantics of task_id are things an agent needs before calling this correctly.

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 all three parameters, so the description must compensate and largely does not. It indirectly hints at the vocabulary inside the decisions array (adopt, correct, exclude), which is genuinely useful, but task_id and especially apply_to_similar — a flag that propagates the decision to other components — are left entirely unexplained.

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 names a specific action set (adopt, correct, or exclude) against a specific target (low-confidence or topologically abnormal components), plus the side effect of recording the adjudication basis. That is a clear verb+resource statement an agent can act on. It falls short of a 5 only because it does not differentiate itself from siblings such as check_model or query_graph, which could plausibly surface the same ambiguities.

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 trigger condition is implied by the target scope: use this when components are low-confidence or topologically anomalous. There is no explicit when-not guidance, no named alternative for merely inspecting ambiguities, and no prerequisite (e.g., that detection must run first). Usage is inferable but not spelled out.

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