Skip to main content
Glama
Sign In
Azure DevOps MCP Server

Azure DevOps MCP Server

by Tiberriver256
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

get_work_item_attachment

Download an Azure DevOps work item attachment and save it locally using the attachment ID from the work item relations.

Instructions

Download an attachment from Azure DevOps and save it to the local filesystem. The attachment ID can be obtained from the work item relations.

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": {
      "attachmentId": "<attachmentId>",
      "outputPath": "<outputPath>"
    },
    "name": "get_work_item_attachment"
  }
}

Input Schema

NameRequiredDescriptionDefault
outputPathYesThe absolute path where the attachment will be saved
attachmentIdYesThe ID (GUID) of the attachment to download. Can be obtained from the work item relations.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.0.6

TDQS

B3.2/5.0
Behavior3/5

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

With no annotations, the description carries the full behavioral burden. It does disclose the key side effect (writes a file to the local filesystem) and that the ID comes from work item relations, but it says nothing about overwrite behavior, required permissions, or failure modes when the path or ID is invalid.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two short, front-loaded sentences with no filler; the action and destination come first. The second sentence largely restates the attachmentId schema description, which is mild redundancy but not bloat.

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?

For a filesystem-writing tool with no annotations and no output schema, the description should say more about what happens on success or failure and whether an existing file is overwritten. It covers the essentials of purpose and ID sourcing but leaves meaningful behavioral gaps.

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%, so both parameters are already documented in the schema, including the same note about obtaining the ID from work item relations. The description adds no syntax, format, or constraint detail beyond the schema, so the baseline of 3 applies.

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?

States a specific verb (download) and resource (attachment) plus the destination (local filesystem), which clearly separates it from create_work_item_attachment and delete_work_item_attachment siblings. It does not explicitly name those siblings, so it falls just short of the top tier.

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 only guidance is where to obtain the attachmentId ('from the work item relations'), which is input sourcing, not usage context. There is no statement of when to use this versus other attachment tools or what prerequisites must be met before downloading.

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