Skip to main content
Glama
Sign In
omni-dev

omni-dev

by rust-works
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Rust
Local

jira_delete

Delete a JIRA issue permanently by providing its key and confirming with true. Irreversible; requires explicit consent to prevent accidental deletions.

Instructions

Delete a JIRA issue. DESTRUCTIVE AND IRREVERSIBLE. You must explicitly pass confirm: true for the deletion to proceed; otherwise the tool returns an error without contacting the API. Returns YAML {status: ok} on success. Mirrors omni-dev atlassian jira delete.

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": {
      "key": "<key>",
      "confirm": "<confirm>"
    },
    "name": "jira_delete"
  }
}

Input Schema

NameRequiredDescriptionDefault
keyYesJIRA issue key to delete (e.g., `PROJ-123`).
confirmYesMust be set to `true` — destructive guard.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.40.0
  2. Removedv0.39.0
  3. Changed2 schema fields changedv0.33.0
    • removedInput schema / description
      Removed value: -"Parameters for the `jira_delete` tool.\n\n`confirm` must be `true` for the deletion to proceed. This is the\nMCP-side guard for an irreversible operation; the assistant must\nexplicitly opt in."
    • removedInput schema / title
      Removed value: -"DeleteParams"
  4. First observedv0.1.0

TDQS

A4.7/5.0
Behavior5/5

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

With no annotations provided, the description fully carries the burden of behavioral disclosure. It prominently warns 'DESTRUCTIVE AND IRREVERSIBLE', explains the confirm guard behavior (returns error without API call), and specifies the success return format (YAML `{status: ok}`). This adds significant value beyond the schema.

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?

Three sentences, front-loaded with the critical destructiveness warning, then the confirm requirement, success payload, and CLI reference. Every sentence earns its place with zero fluff.

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

Completeness5/5

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

For a simple two-parameter delete tool with no output schema, the description covers the essential context: destructive nature, confirmation guard, success response, and equivalent CLI command. It is complete for an agent to select and invoke safely.

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

Parameters4/5

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

The input schema already documents both parameters with 100% coverage, setting a baseline of 3. The description adds behavioral meaning to the `confirm` parameter by explaining the error-if-not-true behavior, and also notes the CLI mirror. This extra context justifies a 4.

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 clearly states 'Delete a JIRA issue' with a specific verb and resource, distinguishing it from sibling delete tools for comments, attachments, sprints, or versions. The scope is unambiguous.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It provides clear operational context by requiring an explicit `confirm: true` guard and noting that the tool will error without contacting the API. It does not explicitly name alternatives or when-not-to-use conditions, but the destructive warning plus confirmation requirement gives enough guidance for a delete operation.

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