Skip to main content
Glama

Download Jira attachment

download_attachment

Save a Jira issue attachment to a local file using issue key and attachment ID; optionally choose the Jira instance and output directory.

Instructions

Download an attachment from a Jira issue to a local file.

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": {
      "issue_key": "<issue_key>",
      "attachment_id": "<attachment_id>"
    },
    "name": "download_attachment"
  }
}

Input Schema

NameRequiredDescriptionDefault
config_idNoJira instance to use, from list_configs. Omit for the default.
issue_keyYesIssue key, e.g. ONE-123.
output_dirNoExisting directory to save into. The file is saved in an <issue_key>/ subdirectory. Default: the server's working directory.
attachment_idYesNumeric attachment ID from get_issue.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.9/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=false, idempotentHint=false, openWorldHint=true and destructiveHint=false, and the description adds little beyond restating that a local file is written. It says nothing about overwrite behavior when the target file already exists, required Jira permissions/auth, size limits, or what happens on failure — the gaps an agent would actually need for a non-idempotent write.

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?

A single front-loaded sentence with zero filler; verb, resource, and destination appear in the first half. Nothing needs trimming and nothing is buried.

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?

With no output schema, the description carries the burden of describing the return value, and it never says whether the tool returns the saved path, bytes written, or nothing — a real gap for a download tool whose caller must locate the file. Overwrite/collision behaviour for a non-idempotent local write is likewise unstated.

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 config_id, issue_key, output_dir and attachment_id are all fully documented in the schema, including the <issue_key>/ subdirectory rule and the default working directory. The description adds no parameter meaning beyond that, which is the expected baseline when the schema carries the load.

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), a specific resource (an attachment from a Jira issue), and the destination (a local file). An agent can distinguish it from the issue CRUD siblings (get_issue, update_issue, add_comment) at a glance, though the description never names an alternative or the retrieval tool that supplies attachment_id.

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?

There is no when-to-use or when-not-to-use guidance; the sentence only describes the operation itself. The one piece of usage-critical information — that attachment_id comes from get_issue — lives in the input schema, not in the description, so the description does nothing to route the agent.

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