Skip to main content
Glama

Unlink a related memory

cut
Destructive

Unlink concepts from another so they no longer show up in its [ YOU MAY ALSO NEED ] list of related memories. The concepts themselves are kept.

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": {
      "suggested": "<suggested>",
      "list_owner": "<list_owner>"
    },
    "name": "cut"
  }
}

Input Schema

NameRequiredDescriptionDefault
suggestedYesThe concepts to take out of the list.
list_ownerYesThe concept whose list it is.

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A3.7/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true and readOnlyHint=false, so the description's job is to add nuance, which it partly does by clarifying that only the link is removed and the concepts survive. It does not say whether the unlink is reversible, what happens if a concept is not currently linked, or whether partial success is possible.

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?

Two short sentences, front-loaded with the action and effect; the preservation note is placed where it matters most. The bracketed UI label is slightly awkward but conveys useful domain context rather than padding.

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 two-parameter mutation with no output schema, the definition covers the action, target, and preservation semantics, but omits edge-case behavior (non-existent links, idempotency) and any note about how the change is confirmed to the caller.

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?

Schema description coverage is 100%, so the baseline is 3; however, the description adds real meaning by pairing the plural 'concepts' with the 'suggested' array (multiple items are removed at once) and framing 'list_owner' as the concept whose list is edited, clarifying the direction of the relationship that the schema alone leaves ambiguous.

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 supplies a concrete verb ('Unlink') and names both the resource (concepts) and the visible effect (removal from the '[ YOU MAY ALSO NEED ]' related list), which the opaque tool name 'cut' does not convey. The closing clause 'The concepts themselves are kept' implicitly distinguishes it from delete_concept/delete_tag, though it does not name them.

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?

Usage is implied rather than stated: an agent can infer this is the tool for removing an existing relation while preserving the concepts. There is no explicit when-to-use/when-not-to-use statement and no named alternative for the case where the agent actually wants to delete the concept itself.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources