Skip to main content
Glama

tracker_download_attachment

Download an issue attachment to a new local file and return its path, original name, size, and SHA256 without changing Tracker.

Instructions

Download an attachment belonging to an issue to a new local file (max 250 MiB). Returns path, original name, size and SHA256. Does not analyze or execute the file. No changes to Tracker.

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": {
      "issueKey": "<issueKey>",
      "attachmentId": "<attachmentId>"
    },
    "name": "tracker_download_attachment"
  }
}

Input Schema

NameRequiredDescriptionDefault
issueKeyYes
attachmentIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4/5.0
Behavior4/5

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

Adds real context beyond the annotations: the 250 MiB cap, the exact returned fields (path, original name, size, SHA256), the guarantee the file is neither analyzed nor executed, and the scoping of mutation to the local filesystem rather than Tracker. The 'No changes to Tracker' note usefully reconciles with readOnlyHint=false (a local file is written). It still says nothing about permissions, auth, or what happens if a file of the same name already exists.

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?

Four short sentences, front-loaded with the action and destination, then constraints, then return payload, then safety notes. No filler or repetition; each sentence adds distinct information.

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?

With no output schema, the description steps in to enumerate the return fields and the size ceiling, and it defines the safety boundary of the write. Only minor gaps remain (how to source an attachmentId, local write location/overwrite behavior), which are small against a two-parameter tool.

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 coverage is 0%, so the description must carry parameter meaning. It conveys the key relationship that attachmentId is scoped within issueKey ('an attachment belonging to an issue'), which is genuine semantic value, but gives no format cues, length limits, or where an agent is expected to find a valid attachmentId.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('Download an attachment belonging to an issue') plus the concrete result ('a new local file'), and the closing clause 'Does not analyze or execute the file' separates it from any inspection/analysis tool. An agent knows immediately this only retrieves bytes, not content interpretation.

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: the wording establishes that the attachment must belong to an issue, which frames the two required identifiers. There is no explicit when-to-use statement, no exclusions versus alternatives, and nothing about how to obtain an attachmentId before calling.

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