Skip to main content
Glama
mcp-devops-onpremise

mcp-devops-onpremise

by zwitbaum

Get work item attachment

devops_work_item_attachment_get
Destructive

Download a work item attachment by ID, returning base64-encoded content or saving it to a local directory when a save path is provided.

Instructions

Download a work item attachment by specified ID. Returns base64-encoded content, or saves to a local directory if savePath is provided.

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": {
      "attachment_id": "<attachment_id>",
      "file_name": "<file_name>"
    },
    "name": "devops_work_item_attachment_get"
  }
}

Input Schema

NameRequiredDescriptionDefault
file_nameYesThe file name of the attachment. Used to determine the MIME type. If save_path is provided, the file is saved under this name.
save_pathNoOptional directory path to save the file to. If omitted, returns the content as a base64-encoded resource. NOTE: relative paths are resolved against the MCP server's working directory; paths starting with '..' are not allowed.
attachment_idYesThe GUID of the attachment.

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.0

TDQS

A3.7/5.0
Behavior3/5

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

Without annotations the description usefully discloses the two operating modes (base64 return vs. writing to disk), which is genuine behavioral context. However, destructiveHint=true and readOnlyHint=false are only partly explained: it does not warn that saving may overwrite an existing file or fail on unwritable directories, which is exactly what the destructive hint implies.

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, purpose first, return-mode behavior second; no filler or restatement of the tool name beyond the minimum needed. Every clause carries information the agent uses when calling it.

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?

An output schema exists, so the description needn't enumerate the response shape, and both return paths are covered. The remaining gap is the local-write side effect (overwrite risk, path restrictions beyond the '..' rule already in the schema) that the destructive annotation flags but the prose never addresses.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3; the description still adds value by tying savePath to a change in return mode and tying file_name to the on-disk name. It adds little beyond the schema text itself, but nothing is misleading.

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 ('work item attachment') plus the lookup key (ID), which is enough to separate it from sibling work-item tools such as devops_work_item_get or comment tools. It doesn't name any sibling explicitly, 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?

Usage is only implied by the resource name – an agent can infer 'use this to fetch an attachment'. There is no explicit when-to-use, no prerequisites (e.g. permissions, attachment size limits), and no guidance versus alternatives like devops_work_item_get or devops_get_item_content_diff.

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