Turbo Quant Memory MCP Server

by Lexus2016

Overview Schema Source Related Servers Discussions Admin

unlink_entities

Remove a Knowledge Graph link between two entities when a relationship is no longer valid, using source and target URIs to keep stored memory accurate.

Instructions

Remove a Knowledge Graph link between two entities.

source_uri / target_uri use the same URI forms as link_entities: note://<note_id>, file://<relative/path>, issue://KEY, https://...

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": {
      "source_uri": "<source_uri>",
      "target_uri": "<target_uri>"
    },
    "name": "unlink_entities"
  }
}

Input Schema

Name	Required	Default
`scope`	No	project
`source_uri`	Yes
`target_uri`	Yes
`relation_type`	No

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.36.1Nov 10, 2026

TDQS

B3.2/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 burden. It does not disclose whether removal is idempotent, what happens if the link is absent, whether the operation is reversible, what permissions or scope are required, or which entity pair must match. For a mutation tool, that is a significant gap.

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 definition is short, front-loaded, and wastes no words; the URI format guidance comes after the purpose statement. The line break and trailing newline are cosmetic issues only.

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?

An output schema exists, so the description need not explain return values. However, for a two-entity mutation with four parameters, it omits how scope and relation_type affect matching and what the behavior is on no-match. This makes it only adequate, not complete.

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%, so the description must compensate. It does add useful meaning for source_uri and target_uri by listing concrete URI forms (note://, file://, issue://, https://), but it says nothing about the scope parameter (which defaults to 'project') or the optional relation_type, leaving half the parameters 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 uses a specific verb and resource: 'Remove a Knowledge Graph link between two entities.' This clearly identifies it as the inverse of link_entities, so an agent can distinguish it from the linking sibling. It does not, however, explicitly name alternatives such as link_entities or get_related_entities.

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 description implies when to use the tool by framing it as removal of an existing link and by pointing to link_entities for URI conventions. It does not state prerequisites, edge cases such as a link that does not exist, or when a different tool should be used instead.

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