Skip to main content
Glama
Sign In
codebugs

codebugs

by faxik
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

relations_unrelate

Retract a relation between findings while preserving its history. Use when a dependency or link should be marked as no longer active without deleting the record.

Instructions

Retract a relation. Tombstones it — the row and its history remain.

Args:

  • src_id: Source finding

  • rel: The relation to retract

  • dst_id: Target finding

  • retracted_by: Who is retracting it

  • reason: Why

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": {
      "src_id": "<src_id>",
      "rel": "<rel>",
      "dst_id": "<dst_id>",
      "retracted_by": "<retracted_by>"
    },
    "name": "relations_unrelate"
  }
}

Input Schema

NameRequiredDescriptionDefault
relYes
dst_idYes
reasonNo
src_idYes
retracted_byYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.2

TDQS

A3.8/5.0
Behavior3/5

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

With no annotations, the description carries full behavioral disclosure burden. It does disclose the key side effect: the relation is tombstoned, not deleted, and history remains. However, it does not address reversibility, idempotence, what happens if the relation is already tombstoned, or any permission requirements. The tombstone disclosure is valuable but incomplete.

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 front-loaded: the first sentence states the core action and likely the most important behavioral detail. The parameter list is clean and every line adds a small semantic increment. No filler or redundancy.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the five parameters, all are covered with at least a basic explanation, the tombstone behavior is disclosed, and an output schema exists so return values need not be described. Minor gaps remain—no mention of failure modes, idempotence, or whether an active relation is required—but the description is sufficient for a competent agent to invoke the tool safely.

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?

The schema has 0% description coverage, so the description must compensate. It provides brief semantic labels for all five parameters—'Source finding', 'Target finding', 'Who is retracting it', 'Why'—which is useful. But 'rel: The relation to retract' is nearly tautological, and no parameter receives format, source, or constraint details 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 states a specific verb and resource: 'Retract a relation.' It adds a clarifying behavioral detail—'Tombstones it — the row and its history remain'—which clearly distinguishes this from deletion and from the sibling relations_relate. The purpose is immediately understandable.

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 implied usage is clear: use this when you want to retract a relation while preserving its history. However, it provides no explicit guidance about when to prefer this tool over alternatives, does not name relations_relate as the counterpart, and gives no conditions or prerequisites such as whether the relation must currently be active.

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

Deploy Server

Other Tools