Skip to main content
Glama

add_issue_attachment

Attach a Base64-encoded file to an existing bug tracker issue. Use it to add logs, screenshots, or documents to a MantisBT issue by passing the issue ID, filename, and encoded content.

Instructions

Adds an attachment file (Base64) to an existing issue.

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>",
      "filename": "<filename>",
      "content_base64": "<content_base64>"
    },
    "name": "add_issue_attachment"
  }
}

Input Schema

NameRequiredDescriptionDefault
filenameYes
issue_idYes
content_base64YesFile content encoded in Base64.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.7/5.0
Behavior2/5

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

With no annotations provided, the description carries the full behavioral burden, but it says nothing about permissions, file-size or content limits, whether an attachment can be replaced or duplicated, or whether the operation is reversible. It only discloses the Base64 encoding and the target being an existing issue.

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 well-formed sentence with no filler, and the key facts (adds, attachment, Base64, existing issue) are front-loaded. Brevity here reflects under-specification rather than wasteful wording.

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?

For a mutation tool with three required parameters, no annotations, and no output schema, the description is too thin: it omits permission/limit behavior, error conditions, and return information. An agent would have to guess at several operational details before calling it safely.

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 only 33%, with only content_base64 documented in the schema. The description adds little beyond repeating that content is Base64; it does not explain filename constraints, that issue_id must reference an existing issue ID, or any encoding/size limits for the payload.

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 pairs a specific verb ("Adds") with a specific resource ("an attachment file") and scopes it to "an existing issue," so the agent knows exactly what the tool does. It does not name or contrast with any sibling such as get_issue_attachment, so it stops short of full differentiation.

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 guidance on when to use this versus alternatives like add_issue_note or get_issue_attachment, nor on prerequisites such as the issue needing to exist or any permission requirement. The only implicit condition is that the issue already exists.

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