Skip to main content
Glama
Sign In
omni-dev

omni-dev

by rust-works
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Rust
Local

jira_changelog

Get the change history for a Jira issue as YAML, listing author, timestamp, and changed items per entry. Use this to audit edits and review issue activity.

Instructions

Get the change history for a JIRA issue. Returns YAML with one entry per change (author, timestamp, items). The author is an Atlassian account ID — resolve it to a display name with jira_user_get. Mirrors omni-dev atlassian jira changelog.

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

Input Schema

NameRequiredDescriptionDefault
keyYesJIRA issue key (e.g., `PROJ-123`).
limitNoMaximum number of entries to return. `0` means unlimited (default 50).

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_changelog` tool."
    • removedInput schema / title
      Removed value: -"ChangelogParams"
  4. First observedv0.1.0

TDQS

A3.8/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does disclose useful behavior: it returns YAML with one entry per change (author, timestamp, items) and notes that the author is an Atlassian account ID needing resolution via jira_user_get. This goes beyond a generic 'get history' and helps the agent understand the output shape and a follow-up step, though it doesn't discuss pagination or potential errors.

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?

The description is front-loaded with the core purpose and contains no filler. Each sentence adds value: the purpose, the output format, the author ID caveat, and the mirroring to a known CLI command. It is compact and well-structured.

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?

Given the simple two-parameter schema, the description adequately covers what the tool returns and highlights an important nuance (author IDs). Since there is no output schema, the explicit mention of 'author, timestamp, items' is valuable. It could be slightly more complete by explaining the 'items' structure, but it is sufficient for a straightforward changelog fetcher.

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 100% — both `key` and `limit` are described with examples and defaults. The description adds no additional parameter semantics beyond what the schema already provides, so the baseline score of 3 is appropriate.

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 the tool's function: 'Get the change history for a JIRA issue.' This is a specific verb+resource combination and distinguishes it from sibling tools like jira_read or jira_search by focusing on history/changelog. It also mentions the YAML return format, further clarifying its unique output.

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 provides no explicit guidance on when to use this tool versus alternatives. It does not mention any exclusions or prerequisites, and the only related tool reference (jira_user_get) is for post-processing author IDs, not for choosing between history and other query methods. The 'Mirrors omni-dev...' line is provenance, not usage guidance.

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