Skip to main content
Glama

delete_issue_relationship

Removes a relationship between two issues in MantisBT using the issue ID and relationship ID, so you can detach linked issues when a relationship is no longer valid.

Instructions

Removes a relationship between issues.

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": {
      "issue_id": "<issue_id>",
      "relationship_id": "<relationship_id>"
    },
    "name": "delete_issue_relationship"
  }
}

Input Schema

NameRequiredDescriptionDefault
issue_idYes
relationship_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.6/5.0
Behavior2/5

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

With no annotations, the description carries the full behavioral burden and mostly fails: it does not say whether deletion is permanent or reversible, what permissions are required, what happens to the reciprocal side of the relationship, or what is returned on success or failure. Only the bare mutation intent is conveyed.

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

Conciseness3/5

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

A single front-loaded sentence with no wasted words, but it is under-specified rather than tight; there is no structure distinguishing behavior, inputs, or effects.

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

Completeness2/5

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

For a destructive two-parameter mutation with no annotations, no output schema, and no parameter documentation, the definition leaves far too much unsaid. An agent could invoke it correctly by name but has no basis for judging safety, scope, or side effects.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% and neither of the two required parameters (issue_id, relationship_id) is explained in the description. It also does not clarify whether relationship_id is globally unique or scoped to issue_id, which is the key ambiguity an agent would face.

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?

"Removes a relationship between issues" names a specific verb (removes) and resource (issue relationship), and the deletion verb implicitly separates it from the sibling add_issue_relationship. It stops short of stating what kind of relationship is removed or whether removal is symmetric.

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?

There is no statement of when to use this versus the sibling add_issue_relationship or whether prerequisites exist (permissions, whether the relationship must already exist). The agent must infer all usage context from the name alone.

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