Alfresco MCP Server

download_document

Retrieve any document from Alfresco by node ID, saving it locally as an attachment or to a custom folder.

Instructions

Download a document from Alfresco repository.

Input Schema

TableJSON Schema

Name	Required	Description
`node_id`	Yes	The Alfresco node ID to download
`attachment`	No	Download as attachment (default: True)
`save_to_disk`	No	Save file to disk (default: True)
`destination_dir`	No	Optional custom destination folder (default: ~/Downloads)

Output Schema

TableJSON Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed10 schema fields changedv1.2.0Sep 21, 2026

addedInput schema / additionalProperties
```
Added value: +false
```

addedInput schema / properties / attachment / description

Added value: +"Download as attachment (default: True)"

removedInput schema / properties / attachment / title
```
Removed value: -"Attachment"
```

addedInput schema / properties / destination_dir

Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "Optional custom destination folder (default: ~/Downloads)"
+}

addedInput schema / properties / node_id / description
```
Added value: +"The Alfresco node ID to download"
```
removedInput schema / properties / node_id / title
```
Removed value: -"Node Id"
```
addedInput schema / properties / save_to_disk / description
```
Added value: +"Save file to disk (default: True)"
```
removedInput schema / properties / save_to_disk / title
```
Removed value: -"Save To Disk"
```
removedOutput schema / properties / result / title
```
Removed value: -"Result"
```
removedOutput schema / title
```
Removed value: -"_WrappedResult"
```

First observedAug 15, 2025

TDQS

C2.8/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 burden of behavioral disclosure, but it only states that it downloads a document. It does not reveal that it can save to disk, whether the download is treated as an attachment, or any side effects on the repository. The behavior is fundamentally opaque beyond the basic action.

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, compact sentence with no filler or redundant phrasing. It is appropriately sized for a simple download action, and the main verb is front-loaded, making it instantly scannable.

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?

Despite having 4 parameters and an output schema, the description omits crucial operational context such as default file save location, handling of existing files, or how the node_id is used. It does not explain return values or error conditions, leaving the agent with significant gaps in how to correctly invoke the tool beyond the schema.

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 description coverage is 100%, so the schema already documents all parameters like node_id, attachment, save_to_disk, and destination_dir. The description adds no additional meaning or context about these parameters, so it neither helps nor hurts beyond the baseline for full schema coverage.

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 states a clear verb ('Download') and resource ('document from Alfresco repository'), making the primary purpose immediately obvious. It distinguishes itself from siblings like upload_document and checkout_document by the action itself, though it does not explicitly name alternatives or scope conditions.

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

Usage Guidelines1/5

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

The description provides no guidance on when to use this tool versus any of the sibling tools (e.g., browse_repository, get_node_properties, or upload_document). It does not mention prerequisites, typical scenarios, or exclusions, leaving the agent without context for selection.

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

Deploy Server