Skip to main content
Glama
Sign In
aspa-mcp

aspa-mcp

by octos-ai
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

Baixar anexos

aspa_download_attachments
Read-only

Downloads conversation attachments—images, documents, audio, and video—to a local folder and returns file paths so they can be opened with the Read tool.

Instructions

Download attachments (images, documents, audio, video) of a conversation to a local folder and return the file paths, so they can be opened with the Read tool. Audio is not transcribed.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "aspa_download_attachments"
  }
}

Input Schema

NameRequiredDescriptionDefault
indexNoIndex from aspa_list_conversations.
contactNoContact name (exact or unique case-insensitive part). Used instead of index.
loadMoreTimesNo
messageIndexesNoItem indexes from aspa_read_conversation. Omit for all.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.8.0

TDQS

A4/5.0
Behavior4/5

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

Annotations only say readOnlyHint and openWorldHint; the description adds real behavioral facts beyond them, namely that files are written to a local folder (a filesystem side effect despite the read-only hint) and that the return value is file paths. The explicit limitation 'Audio is not transcribed' pre-empts a likely wrong assumption.

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?

A single front-loaded sentence: action, resource, destination, return value, then the caveat. Every clause carries information and nothing is padded.

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?

No output schema exists, so the description must state the return value, and it does (file paths that can be read). Combined with the audio caveat and the in-schema parameter docs, an agent has enough to invoke it correctly; only the loadMoreTimes behavior and what happens when a conversation has no attachments are left unstated.

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 75%, with index, contact and messageIndexes already documented in-schema; the description adds no meaning to any of them. The undocumented loadMoreTimes parameter is not explained anywhere, so the description does not compensate for the remaining gap. Baseline 3 applies.

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 (download) and resource (attachments) with an enumerated scope (images, documents, audio, video) plus the side effect destination (a local folder) and return value (file paths). A reader can tell it apart from aspa_send_attachment or aspa_transcribe_audio, though it never names a sibling explicitly.

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?

Gives clear context for use: fetch files so they 'can be opened with the Read tool', which tells the agent this is a precursor step to inspection. The clause 'Audio is not transcribed' implicitly points to aspa_transcribe_audio as the alternative for audio content, but it does not say so outright and offers no guidance on choosing between the index and contact parameters.

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