Skip to main content
Glama
mcp-devops-onpremise

mcp-devops-onpremise

by zwitbaum

Get work item

devops_work_item_get
Read-only

Retrieve a single Azure DevOps work item by numeric ID to view its key fields, attachments, and linked items in one compact response.

Instructions

Retrieve a single work item by numeric ID. Returns a compact object with key fields (title, state, type, assignee, description, acceptance criteria, tags, parent), plus attachments (files and inline images) and linked items (work items, pull requests, commits).

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": {
      "work_item_id": "<work_item_id>"
    },
    "name": "devops_work_item_get"
  }
}

Input Schema

NameRequiredDescriptionDefault
work_item_idYesThe numeric work item ID to fetch.

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.0

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety is covered; the description goes further by enumerating what is returned (key fields, attachments including inline images, and linked items such as pull requests and commits). That return-shape context is genuinely additive, though it omits behavior on a missing or inaccessible ID.

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 tight sentences with the core action front-loaded and the return contents summarized afterward. Every clause carries information; there is no filler or repetition of the title.

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 single-parameter read tool with annotations and an output schema present, the definition covers action, input, and output shape adequately. The enumeration of returned fields partly duplicates the output schema and nothing is said about failure modes, which keeps it just short of full marks.

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?

There is a single required parameter with 100% schema description coverage, so the schema already documents work_item_id as the numeric ID to fetch. The description reinforces 'numeric ID' but adds no format, range, or scoping detail beyond that baseline.

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 states a specific verb and resource ('Retrieve a single work item') and narrows the lookup to a 'numeric ID', which implicitly contrasts with the search/query siblings. It stops short of naming any alternative tool, so it is clear but not fully differentiated by explicit reference.

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?

Usage is only implied: 'by numeric ID' signals this is the direct-fetch path versus devops_work_item_search or devops_work_item_query_by_wiql, but the description never says when to prefer this tool or what to do if only a title/text is known. No exclusions or prerequisites are given.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.