Skip to main content
Glama
mcp-server-redmine

mcp-server-redmine

by jesusr00

delete_issue_relation

Permanently deletes a Redmine issue relation by numeric ID, removing unwanted links between issues. This action cannot be undone.

Instructions

[Alpha] Permanently delete a Redmine issue relation by its numeric ID. This action cannot be undone.

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": {
      "id": "<id>"
    },
    "name": "delete_issue_relation"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.8.1
    • removedInput schema / additionalProperties
      Removed value: -false
    • addedInput schema / properties / id / maximum
      Added value: +9007199254740991
  2. First observedv0.3.0

TDQS

A3.6/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full burden. It does disclose the most important behavioral trait — permanence and irreversibility ('cannot be undone') — but says nothing about permission/auth requirements, behavior when the ID does not exist, or what is returned after deletion.

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?

Two short sentences with the action and its irreversible nature front-loaded. Aside from the '[Alpha]' prefix, every word contributes and there is no redundant filler.

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?

For a single-parameter destructive tool this is largely sufficient: purpose, target identifier, and irreversibility are all covered. With no output schema present, a brief note on what is returned on success or failure would complete it, but the core is adequate.

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 coverage is 0% for the single required 'id' parameter, so the description must compensate. It adds useful disambiguation by specifying the ID is the numeric relation ID (not an issue ID), but provides no format, range, or example details beyond that.

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?

States a specific verb ('Permanently delete') and resource ('Redmine issue relation') plus the identifier type ('numeric ID'). This cleanly separates it from siblings like redmine_delete_issue, redmine_delete_wiki_page and get_issue_relation/create_issue_relation without needing schema inspection.

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 explicit when-to-use guidance, no mention of alternatives (e.g., deleting the issue itself vs. only the relation), and no preconditions such as requiring the relation to exist or specific permissions. Usage is only implied by the verb and resource.

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