Skip to main content
Glama

delete_issue

Deletes a MantisBT issue by ID to remove outdated, duplicate, or invalid bug reports from the tracker.

Instructions

Deletes a MantisBT issue by ID.

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>"
    },
    "name": "delete_issue"
  }
}

Input Schema

NameRequiredDescriptionDefault
issue_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.9/5.0
Behavior2/5

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

With no annotations supplied, the description carries the full behavioral burden for a destructive operation, yet it discloses nothing beyond the verb. It does not say whether the deletion is permanent or soft, whether attached notes/relationships/tags are cascaded or orphaned, whether elevated permissions are required, or what is returned or raised on failure.

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?

A single front-loaded sentence with zero filler or repetition. Its terseness is a completeness problem rather than a verbosity problem, but the sentence is so short that it does little structuring work.

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 high-consequence destructive tool with no annotations and no output schema, the description should at minimum flag irreversibility and side effects. As written, an agent knows only the verb and the key, leaving the risk profile of the call entirely undisclosed.

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%, but there is only one parameter and the phrase 'by ID' combined with 'issue' makes clear that issue_id is the target issue's numeric identifier. The description adds no range, format, or example semantics beyond that bare association, so it only marginally improves on the schema.

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?

States a specific verb plus resource ('Deletes a MantisBT issue') and the lookup key ('by ID'), which implicitly separates it from siblings like delete_issue_note and delete_issue_relationship. It does not explicitly name those siblings or state that notes/relationships survive the delete, so it stops short of a 5.

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 when-to-use or when-not-to-use guidance, no mention of prerequisites such as permissions or issue state, and no pointer to alternatives (e.g. closing or updating an issue instead of deleting it). The agent must infer all routing decisions 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.