RCA-MCP Connector

Overview Schema Source Related Servers Score Discussions Admin

rca_dtree_answer

Answer the current diagnostic question to advance the root cause analysis decision tree. Continue until the session resolves with a diagnosis, confidence score, and recommended repair actions.

Instructions

🌟 Starter+ — Answer the current diagnostic question to advance the decision tree. Call repeatedly until status == "resolved".

Once resolved, use rca_guide_generate_report to turn the session into a shareable report.

Args: params (DTreeAnswerInput): session_id, answer (yes|no|unknown), measurement - ai_summary: also generate a short NL executive summary if this answer resolves the session (Starter+, quota-limited -- see field description)

Returns: str: JSON with status, question OR diagnosis, progress_pct, and ai_summary/ai_summary_error if ai_summary=true was requested and the session resolved. Diagnosis fields (when resolved): diagnosis, confidence, actions, parts_to_check, estimated_repair_time, escalate_to_specialist, fault_codes, references, diagnostic_path

Input Schema

TableJSON Schema

Name	Required	Description	Default
`params`	Yes

Output Schema

TableJSON Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedv4.1.18Sep 10, 2026

addedInput schema / $defs / DTreeAnswerInput / properties / ai_summary

Added value: +{
+  "default": false,
+  "description": "If this answer resolves the session, also generate a short plain-English executive summary of the diagnosis via Claude Haiku (platform-provided key). Starter+ only, subject to the same monthly quota as rca_analysis_run's ai_summary (Starter 100, Pro 1000, Enterprise unlimited) -- see ai_summary/ai_summary_error in the response. Ignored while status is still in_progress.",
+  "title": "Ai Summary",
+  "type": "boolean"
+}

Changed2 schema fields changedv4.1.15Sep 8, 2026
- addedInput schema / $defs / DTreeAnswerInput / properties / client_id / description
```
Added value: +"Client namespace ID"
```
- addedInput schema / $defs / DTreeAnswerInput / properties / token / description
```
Added value: +"API key to authenticate this request"
```
First observedv4.1.13Jul 27, 2026

TDQS

A4.6/5.0

Behavior4/5

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

The description discloses key behavioral aspects: the iterative nature (call repeatedly), the response structure (status, question/diagnosis, progress_pct, ai_summary/error), and quota limits on ai_summary. It does not contradict annotations (readOnlyHint=false, destructiveHint=false). While it doesn't mention authentication (token is in schema) or error handling, it adds value beyond schema by describing the quota and the resolution trigger. Given the sparse annotations, this is strong transparency.

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 well-structured with an Args and Returns section, and the purpose is front-loaded. It is slightly verbose with the emoji and 'Starter+' branding, but every sentence carries meaning. The instructions about repeated calls and follow-up report generation are concise. It earns a high score but loses a point for minor verbosity and unnecessary branding elements.

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 is complete for a stateful tool in a multi-step workflow. It explains the iteration requirement, the resolution condition, the follow-up report tool, and the response format. It covers both the ai_summary generation and its quota. Since the output schema is present, the return fields are already specified. Nothing essential for correct usage is missing.

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

Parameters4/5

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

The schema already provides descriptions for all parameters (token, answer, client_id, ai_summary, session_id, measurement), so baseline is 3. The description adds contextual meaning by explaining the answer values ('yes|no|unknown'), the purpose of measurement ('Optional actual reading'), and the ai_summary behavior ('if this answer resolves the session'). It does not mention token/client_id, but those are self-explanatory. Overall, it enhances the parameter understanding beyond the raw schema.

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's purpose: 'Answer the current diagnostic question to advance the decision tree.' It identifies the specific verb (answer), resource (diagnostic question), and the action's effect (advance the tree). This distinguishes it from siblings like rca_dtree_start (starts a session) and rca_guide_generate_report (generates a report), which are mentioned as follow-up steps.

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?

Explicitly states the calling pattern: 'Call repeatedly until status == "resolved".' It also provides the next step after resolution: 'use rca_guide_generate_report to turn the session into a shareable report.' Additionally, it clarifies the ai_summary parameter's behavior ('if this answer resolves the session') and quota limits, giving the agent clear guidance on when and how to use the tool.

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

Install Server