Skip to main content
Glama
Sign In
mcp-jira-confluence-corp

mcp-jira-confluence-corp

by mshegolev
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

jira_assign_issue

Idempotent

Assign a Jira issue to a user or remove the current assignee.

Instructions

Assign or unassign a Jira issue.

Pass assignee=null to remove the current assignee.

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": {
      "params": "<params>"
    },
    "name": "jira_assign_issue"
  }
}

Input Schema

NameRequiredDescriptionDefault
paramsYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.1

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already indicate idempotentHint=true and non-destructive. The description adds the note about passing null to unassign, which clarifies a behavioral detail. However, it omits permissions or side effects, which would be helpful for a mutation tool.

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 sentences, front-loaded with the main action, and no superfluous words. Efficiently conveys the core function and a special case.

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 simple assignment/unassignment tool, the description covers the essential functionality. An output schema exists (not shown) to describe return values, so the description does not need to. It provides enough context for an AI agent to understand the tool's purpose, though it could mention the required issue_key.

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?

The schema provides full descriptions for both parameters (issue_key and assignee), so baseline is 3. The tool description does not add new parameter information beyond what's in the schema (the null usage is duplicate). Thus, marginal extra value.

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?

The description clearly states 'Assign or unassign a Jira issue' with a specific verb and resource. It distinguishes from siblings like jira_update_issue via its name and focused action, but does not explicitly mention when to use this over alternatives.

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?

No guidance on when to use this tool versus alternatives such as jira_update_issue. The description only states what it does without contextual usage advice.

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