Skip to main content
Glama
Sign In
mcp-atlassian-extended

mcp-atlassian-extended

by vish288
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Jira Download Attachment

jira_download_attachment

Download a Jira attachment to the download directory with a bare file name. Existing files are not overwritten; a numeric suffix is added and the absolute path is returned.

Instructions

Download a Jira attachment into the download directory (default ./atlassian-downloads/).

save_path is a bare file name, not a path. Existing files are never overwritten — a numeric suffix is added — and the final absolute path is returned.

Input Schema

NameRequiredDescriptionDefault
save_pathYesFile name (no directories) to save under the download dir
content_urlYesAttachment content URL

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv0.15.1
    • changedInput schema / properties / save_path / description
      Previous value: -"Local path to save the file"New value: +"File name (no directories) to save under the download dir"
    • removedInput schema / properties / save_path / minLength
      Removed value: -1
    • changedOutput schema / (root)
      Previous value: -{
-  "properties": {
-    "result": {
-      "type": "string"
-    }
-  },
-  "required": [
-    "result"
-  ],
-  "type": "object",
-  "x-fastmcp-wrap-result": true
-}New value: +null
  2. First observedv0.6.13

TDQS

A3.7/5.0
Behavior4/5

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

Goes meaningfully beyond the annotations by disclosing overwrite behavior (never overwrites; numeric suffix added) and the returned absolute path, which the readOnlyHint=false/openWorldHint=true flags alone would not reveal. It could still note required permissions or failure modes, but the mutation semantics are well covered.

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?

Front-loads the purpose in the first sentence and follows with the two behavioral caveats that matter. Every sentence carries information; sizing is appropriate with no filler.

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 correctly explains the return value (final absolute path) and destination behavior, which is what an agent needs to call it. Minor gap: no hint on where content_url comes from or error conditions.

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 100%, so the schema already documents both parameters. The description reinforces that save_path is a bare file name and supplies the default download directory, adding minor value beyond the schema but no syntax or format detail the schema lacks.

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 and resource ('Download a Jira attachment') plus the destination directory, so the action is unambiguous. It does not explicitly distinguish itself from nearby siblings like jira_get_attachments (list) or jira_upload_attachment (reverse direction), leaving a small sibling-overlap risk.

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 implied by the clear purpose and the save_path caveat, but there is no explicit when-to-use guidance or routing away from jira_get_attachments. Nothing tells the agent how to obtain content_url or when this is preferred over the list tool.

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

Deploy Server

Other Tools