Azure DevOps MCP Server

get_work_item_attachments

Retrieve all attachments like files, images, and documents from an Azure DevOps work item by specifying its ID.

Instructions

List all attachments on a work item (files, images, documents).

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": {
      "workItemId": "<workItemId>"
    },
    "name": "get_work_item_attachments"
  }
}

Input Schema

Name	Required	Description	Default
`workItemId`	Yes	Work item ID

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Apr 18, 2026

TDQS

C2.9/5.0

Behavior2/5

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

No annotations are provided, so the description carries the full burden. It states it 'lists all attachments' but doesn't disclose behavioral traits like pagination, rate limits, authentication requirements, error handling, or what 'all' entails (e.g., if it includes deleted attachments). This leaves significant gaps for a tool that likely interacts with a data system.

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 a single, efficient sentence with no wasted words. It front-loads the core purpose ('List all attachments on a work item') and adds clarifying detail ('files, images, documents') without redundancy.

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

Completeness2/5

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

Given no annotations and no output schema, the description is incomplete. It doesn't explain what the output looks like (e.g., list format, attachment metadata), behavioral constraints, or error cases. For a tool with one parameter but potentially complex return data, this lacks sufficient context for reliable agent use.

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 input schema has 100% description coverage, with workItemId clearly documented. The description adds no parameter-specific information beyond implying the tool operates on a work item, which is already evident from the schema. This meets the baseline of 3 since the schema does the heavy lifting.

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 the action ('List all attachments') and resource ('on a work item'), specifying the types of attachments (files, images, documents). It distinguishes from siblings like get_work_item_comments or get_work_item_updates by focusing on attachments, but doesn't explicitly differentiate from other attachment-related tools (none exist in the sibling list).

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 is provided. The description doesn't mention prerequisites, limitations, or when other tools might be more appropriate, such as using get_work_item for general work item details or get_work_item_updates for attachment history.

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

Deploy Server