Skip to main content
Glama

get_issue_attachment

Downloads the content of a specific issue attachment as text or Base64 so the LLM can inspect it.

Instructions

Downloads the content (text or Base64) of a specific issue attachment for inspection by the LLM.

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_id": "<issue_id>",
      "attachment_id": "<attachment_id>"
    },
    "name": "get_issue_attachment"
  }
}

Input Schema

NameRequiredDescriptionDefault
issue_idYes
attachment_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.2/5.0
Behavior3/5

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

With no annotations supplied, the description carries the full behavioral burden, and it does disclose the return encoding (text or Base64), which is the most important trait for how the agent must consume the result. It omits other relevant behavior: size or truncation limits, permission/auth requirements, and what happens when the attachment is missing or binary.

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?

A single front-loaded sentence with no filler; the key information (download, attachment content, encoding) appears immediately. It is lean to the point of being slightly under-specified, but no sentence is wasted.

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?

There is no output schema and no annotations, so the description is the only source of return-value information, and it does state that content comes back as text or Base64. However, for a content-fetching tool it should also cover size limits, error behavior for missing attachments, and whether the Base64 payload needs decoding.

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

Parameters2/5

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

Schema description coverage is 0% for two required integer parameters, so the description must compensate, and it only vaguely gestures at them via "issue" and "attachment" without explaining what an attachment_id is, where to obtain it, or how the two IDs relate. The agent gets no format or sourcing guidance beyond what the bare property names already convey.

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 gives a specific verb and resource ("Downloads the content ... of a specific issue attachment") and even names the return encodings (text or Base64), so an agent knows exactly what the tool retrieves. It does not explicitly contrast itself with the sibling add_issue_attachment, but the add/get verb distinction makes the split obvious.

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?

The phrase "for inspection by the LLM" implies the intended use case (reading attachment contents rather than managing attachments), which is a modest but real signal. There is no explicit when-to-use vs. when-not guidance, no mention of an alternative such as get_issue_full_context for inspecting an issue wholesale, and no stated caveats for large or binary files.

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