Skip to main content
Glama
Sign In
omni-dev

omni-dev

by rust-works
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Rust
Local

jira_sprint_issues

List JIRA sprint issues by sprint ID with optional JQL filter, returning YAML output for agile team tracking and reporting.

Instructions

List issues in one JIRA sprint (get sprint IDs from jira_sprint_list). Accepts an optional JQL filter. Returns YAML. For every issue on a board regardless of sprint, use jira_board_issues instead. Mirrors omni-dev atlassian jira sprint issues.

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": {
      "sprint_id": "<sprint_id>"
    },
    "name": "jira_sprint_issues"
  }
}

Input Schema

NameRequiredDescriptionDefault
jqlNoOptional JQL to further filter issues.
limitNoMaximum number of issues to return. `0` means unlimited (default 50).
sprint_idYesSprint ID.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.39.0
  2. Removedv0.39.0
  3. Changed2 schema fields changedv0.33.0
    • removedInput schema / description
      Removed value: -"Parameters for the `jira_sprint_issues` tool."
    • removedInput schema / title
      Removed value: -"SprintIssuesParams"
  4. First observedv0.1.0

TDQS

A4.1/5.0
Behavior3/5

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

No annotations provided, so description carries burden. Discloses output format (YAML) and refers to a command-line mirror. Does not mention pagination, rate limits, or confirmation that it's read-only, but the return format is useful behavioral info.

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 short sentences covering purpose, usage, sibling distinction, and reference command. No fluff, front-loaded with key action.

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?

Given no output schema, description provides return format (YAML), links to related tools, explains limit behavior, and references parent command. Sufficient for agent to understand and invoke correctly.

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%; all parameters have descriptions. The description repeats JQL as optional and 'limit' default, adding little beyond schema. Baseline 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?

Explicitly states 'List issues in one JIRA sprint' (verb+resource+scope), mentions sprint ID source from sibling tool, and distinguishes from `jira_board_issues` for board-wide queries.

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?

Provides clear context: get sprint IDs from `jira_sprint_list`, optional JQL filter, and alternative `jira_board_issues` for cross-sprint board queries. Lacks explicit when-not-to-use beyond that.

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