RCA-MCP Connector

by dave1362

Overview Schema Source Related Servers Score Discussions Admin

Python

Remote

rca_graph_remove_edge

Destructive

Remove a directed edge between source and target to fix an incorrect causal link or a disproven hypothesis.

Instructions

Remove a directed edge (source → target) from a causal graph. Destructive and irreversible via this tool — undo by re-adding the edge with rca_graph_add_edge, or restoring an earlier version with rca_graph_restore_version.

Use this when an edge was added in error or a causal hypothesis is disproven. Use rca_graph_remove_node instead if you want the node itself gone — that already removes all its edges, so you don't need to remove them individually first.

Args: params (RemoveEdgeInput): - graph_id: the graph to modify - source, target: exact node names (case-sensitive); the edge must currently exist — check with rca_graph_get if unsure

Returns: str: JSON {removed_edge: "source → target"}, or a not_found/value error if the edge or either node doesn't exist

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.

Changed2 schema fields changedv4.1.15Sep 8, 2026
- addedInput schema / $defs / RemoveEdgeInput / properties / client_id / description
```
Added value: +"Client namespace ID"
```
- addedInput schema / $defs / RemoveEdgeInput / properties / token / description
```
Added value: +"API key to authenticate this request"
```
Changed3 schema fields changedv4.1.14Sep 7, 2026
- addedInput schema / $defs / RemoveEdgeInput / properties / graph_id / description
```
Added value: +"Graph to modify"
```
- addedInput schema / $defs / RemoveEdgeInput / properties / source / description
```
Added value: +"Exact source node name (case-sensitive); the edge source→target must currently exist"
```
- addedInput schema / $defs / RemoveEdgeInput / properties / target / description
```
Added value: +"Exact target node name (case-sensitive)"
```
First observedv4.1.13Jul 27, 2026

TDQS

A4.9/5.0

Behavior5/5

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

The description explicitly notes the operation is destructive and irreversible via this tool, and provides undo alternatives: re-add the edge with rca_graph_add_edge or restore an earlier version. It also states the edge must currently exist and describes the return value and error conditions, matching the destructiveHint and idempotentHint annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is concise and well-structured, with no redundant sentences. Each sentence serves a purpose: stating the action, noting destructiveness and undo options, providing usage context, and explaining parameters and return values.

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 provides a complete context for calling the tool: what it does, when to use it, how to undo it, important parameter constraints, and expected return/error behavior. It is sufficient for an agent to invoke this tool correctly without needing additional external information.

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 description adds meaningful semantics for graph_id, source, and target by explaining exact node names are case-sensitive and the edge must currently exist. The token and client_id parameters are not described in prose, but they are already well-described in the schema, so the description still adds value beyond the 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 removes a directed edge (source → target) from a causal graph, using a specific verb and resource. It also differentiates from related sibling tools like rca_graph_remove_node, rca_graph_add_edge, and rca_graph_restore_version.

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?

The description gives explicit when-to-use guidance: use when an edge was added in error or a causal hypothesis is disproven. It also directs users to rca_graph_remove_node instead when removing a node, and suggests rca_graph_get to verify edge existence.

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

Install Server