Slipbox MCP Server

Overview Schema Source Related Servers Discussions Admin

slipbox_remove_link

Remove a link between two notes by specifying source and target IDs. Optionally delete links in both directions to clean up bidirectional connections.

Instructions

Remove a link between two notes.

Args: source_id: ID of the source note target_id: ID of the target note bidirectional: If true, removes links in both directions

Input Schema

TableJSON Schema

Name	Required	Description	Default
`source_id`	Yes
`target_id`	Yes
`bidirectional`	No

Output Schema

TableJSON Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedv1.5.4Sep 22, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "result": {
+      "title": "Result",
+      "type": "string"
+    }
+  },
+  "required": [
+    "result"
+  ],
+  "title": "slipbox_remove_linkOutput",
+  "type": "object"
+}

First observedv0.1.0Aug 2, 2026

TDQS

B3.1/5.0

Behavior2/5

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

No annotations are provided, so the description carries the full behavioral disclosure burden. It states the removal operation and the bidirectional option, but does not disclose idempotency, behavior when the link does not exist, side effects, or whether the operation is reversible—important gaps for a destructive action.

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 compact and well-structured: one clear purpose sentence followed by a scannable argument list. There is no filler or repetition beyond the necessary parameter explanations.

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?

For a simple three-parameter scalar tool with an output schema, the core invocation is understandable. However, the lack of sibling differentiation and the absence of behavioral guidance around a destructive operation make the description incomplete for a fully informed tool selection.

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%, and the description adds definitions for source_id, target_id, and bidirectional, which is helpful. However, the definitions are minimal and mostly restate the parameter names; they do not specify ID formats, lookup semantics, or additional constraints beyond what the schema already shows.

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 clearly states the action and resource: 'Remove a link between two notes.' However, it does not differentiate this tool from the sibling slipbox_delete_link, which appears to have an overlapping purpose, so it stops short of full sibling-level clarity.

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?

The description offers no guidance on when to use this tool instead of slipbox_delete_link or any other alternative. It only explains parameters, leaving the agent to infer the intended context from the tool name.

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