Skip to main content
Glama
Sign In
Jira Cloud MCP Server

Jira Cloud MCP Server

by pascalhubacher
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

remove_vote

Delete a vote cast on a Jira issue using its ID or key.

Instructions

Delete vote

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": {
      "issueIdOrKey": "<issueIdOrKey>"
    },
    "name": "remove_vote"
  }
}

Input Schema

NameRequiredDescriptionDefault
issueIdOrKeyYesThe ID or key of the issue.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2/5.0
Behavior1/5

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

No annotations are provided, so the description must carry the full burden of behavioral disclosure. It only restates the action and reveals nothing about irreversibility, permissions, idempotency, whether a prior vote is required, or what happens 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.

Conciseness2/5

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

The description is only two words, making it concise but under-specified rather than properly structured. It omits the issue target, vote owner, and any usage context that would make the short length effective.

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 one-parameter tool with no annotations and no output schema, this description is insufficient. An agent would not know whose vote is deleted, whether the voter must be the current user, or what the expected outcome is.

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 100%: issueIdOrKey is clearly documented as the ID or key of the issue. The description adds no parameter meaning, but the schema already provides adequate semantic coverage, so the baseline score of 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose2/5

Does the description clearly state what the tool does and how it differs from similar tools?

"Delete vote" simply restates the tool name remove_vote with synonyms. It does not specify whose vote is deleted, that it targets an issue, or how it differs from siblings like add_vote and get_votes beyond the verb.

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?

The description gives no guidance on when to use this tool versus alternatives, no prerequisites, and no conditions. The sibling list includes add_vote and get_votes, but the description does not help an agent decide which operation is appropriate.

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