RCA-MCP Connector

Overview Schema Source Related Servers Discussions Admin

rca_graph_merge

Merge two causal graphs into a unified graph for cross-system root cause analysis, combining network and application layers while handling duplicate edges and preventing cycles.

Instructions

Merge two causal graphs into a unified graph for cross-system RCA (e.g. combining a network-layer graph with an application-layer graph). Duplicate edges keep the higher-weight version; edges that would introduce a cycle are dropped and counted, not silently ignored. Requires the causal_discovery feature (Pro+); both source graphs must belong to you.

Args: params (GraphMergeInput): - graph_id_a, graph_id_b: the two graphs to merge (both must be yours) - merged_name: name for the new, third graph created by this call (graph_id_a/b are left untouched) - conflict_resolution: "union" (default -- keep all nodes from both graphs) or "intersection" (only nodes present in both)

Returns: str: JSON {merged_graph_id, node_count, edge_count, cycles_removed}, or a not_found error if either graph doesn't exist or belongs to another user

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": {
      "params": "<params>"
    },
    "name": "rca_graph_merge"
  }
}

Input Schema

Name	Required	Description	Default
`params`	Yes

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

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

TDQS

A4.7/5.0

Behavior5/5

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

Beyond the sparse annotations (readOnlyHint, openWorldHint, idempotentHint, destructiveHint all false), the description reveals key behaviors: duplicate edges keep the higher-weight version, cycle-introducing edges are 'dropped and counted, not silently ignored', source graphs are 'left untouched', and a not_found error is returned for missing or foreign graphs. This is substantial context the annotations do not convey.

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 front-loaded with purpose and behavioral rules, then cleanly organized into Args and Returns sections with every sentence carrying information. It is on the longer side and the Args section partially duplicates the schema, but the added ownership and side-effect notes justify the length.

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?

For a mutation tool with sparse annotations, the description covers purpose, prerequisites, side effects, edge-conflict behavior, parameter semantics, return format, and error conditions. An agent has everything it needs to select and correctly invoke this tool; the optional output schema only reinforces the documented return value.

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

Parameters5/5

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

Even though the context signal reports 0% schema description coverage, the description compensates fully in its Args section: it adds ownership semantics ('both must be yours'), side-effect clarification ('graph_id_a/b are left untouched'), and explains conflict_resolution ('union' default keeps all nodes, 'intersection' keeps only shared nodes). This adds meaning well beyond the schema's terse property descriptions.

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 opens with a specific verb+resource: 'Merge two causal graphs into a unified graph for cross-system RCA', with a concrete example (combining network-layer with application-layer graphs). This clearly distinguishes it from sibling graph tools like rca_graph_create, rca_graph_add_node, or rca_graph_get.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides clear usage context via the cross-system RCA example and explicit prerequisites ('Requires the causal_discovery feature (Pro+); both source graphs must belong to you'). It does not explicitly name alternatives or state when-not-to-use scenarios, so it stops short of a 5.

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

Deploy Server