Skip to main content
Glama

Fetch shipped work items

fetch_work_items
Read-only

Read completed issues, work items, and merged pull requests from GitHub, Jira, Linear, or Azure DevOps by date range, fix version, or iteration for release-note drafting.

Instructions

Read completed issues, work items and merged pull requests from GitHub, Jira, Linear or Azure DevOps for a date range, fix version or iteration. Read-only.

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": {
      "source": "<source>"
    },
    "name": "fetch_work_items"
  }
}

Input Schema

NameRequiredDescriptionDefault
jqlNoJira only: custom JQL. Overrides project, fixVersion and dates.
repoNoGitHub only: repository as "owner/name".
teamNoLinear only: team key, e.g. "ENG".
wiqlNoAzure DevOps only: custom WIQL. Overrides project, iteration and dates.
limitNoMaximum items to fetch (default 200, max 500).
sinceNoInclude work closed on or after this date (YYYY-MM-DD).
untilNoInclude work closed on or before this date (YYYY-MM-DD).
sourceYesWhich tracker to read from.
projectNoJira project key (e.g. "PAY") or Azure DevOps project name (e.g. "Payments").
iterationNoAzure DevOps only: iteration path, including child iterations, e.g. "Payments\Sprint 42".
fixVersionNoJira only: fix version, e.g. "2.4.0".

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, and the trailing 'Read-only' merely restates that. The description adds genuine context by disclosing that it reaches across four external trackers and that filtering is by closure date/version/iteration. It says nothing about pagination behavior, rate limits, or how results from different sources are combined.

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, no filler, and the resource scope is front-loaded ahead of the source list. The trailing 'Read-only' is the only arguably redundant clause, and it is a single word-level addition.

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

Completeness3/5

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

With 11 parameters and no output schema, the description should say more about what comes back — whether results are normalized across trackers, what item fields are included, or what happens when source-specific filters are mismatched. It covers scope and filter modes adequately but leaves the return shape and cross-source semantics unexplained.

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%, and the schema itself already tags each parameter with its source constraint ('Jira only', 'GitHub only', etc.). The description only summarizes the filter dimensions ('date range, fix version or iteration'), adding little beyond what the schema documents. Baseline 3 is appropriate.

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 gives a specific verb ('Read') and a concrete resource set ('completed issues, work items and merged pull requests') across four named trackers. An agent knows immediately this is a completed-work retrieval tool. It does not explicitly contrast with the sibling draft_release_notes, so it falls short of a 5.

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

Usage Guidelines3/5

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

It states the filter modes available (date range, fix version, iteration), which implies when the tool is applicable, but never says when to prefer it over other tools or when it should not be used. With only one sibling and no explicit routing, usage is implied rather than guided.

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