Skip to main content
Glama
Sign In
mcp-confluence

mcp-confluence

by sirexelite
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Скачать вложение

confluence_download_attachment

Downloads a Confluence attachment from a download URL and saves it to a specified local file path.

Instructions

Скачивает вложение по download-ссылке (из confluence_list_attachments) и сохраняет на диск.

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": {
      "downloadUrl": "<downloadUrl>",
      "savePath": "<savePath>"
    },
    "name": "confluence_download_attachment"
  }
}

Input Schema

NameRequiredDescriptionDefault
savePathYesКуда сохранить файл на диске
downloadUrlYesСсылка для скачивания (downloadUrl из списка вложений)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4.2/5.0
Behavior3/5

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

With no annotations, the description carries full burden. It states the tool downloads and saves to disk, but does not disclose details about overwriting, error handling, permissions, or size limits. The behavior is adequately described for basic use but lacks depth.

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?

The description is a single, efficient sentence that states the action and dependencies. No unnecessary words or redundancy. It is front-loaded with the core verb and object.

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?

For a simple two-parameter download tool with no output schema or annotations, the description covers the essential use case. It could be enhanced by mentioning overwrite behavior or permission requirements, but it is sufficient for basic agent interaction.

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

Parameters4/5

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

Schema coverage is 100% with descriptions for both parameters. The description adds value by specifying that the downloadUrl originates from confluence_list_attachments and that the file is saved to disk, reinforcing the purpose of savePath. This exceeds the baseline of 3.

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?

The description clearly states the tool downloads an attachment using a download link and saves it to disk. It references the specific source of the URL (confluence_list_attachments), distinguishing it from sibling tools like upload_attachment.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implicitly indicates when to use the tool (when you have a download URL from list_attachments). It does not explicitly exclude alternatives, but the context and sibling tools provide clear differentiation.

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