Skip to main content
Glama
bruhsb
by bruhsb

paperclip_download_attachment

Read-only

Download an attachment's content by its UUID. Retrieve base64-encoded file data along with metadata like content type and size, returning either a markdown summary or full JSON envelope.

Instructions

Fetch the content of an attachment by ID from the Paperclip API.

Args:

  • attachmentId: string — Attachment UUID (example: "att_abc123")

  • response_format: 'markdown' | 'json' — Output format (default 'markdown')

Returns: Returns a fixed envelope with fields: attachmentId, contentType, size (bytes), contentBase64 (base64-encoded file content). When response_format is 'markdown', produces a compact summary (id, contentType, size, base64 snippet). When response_format is 'json', returns the full envelope as structured JSON.

Examples:

  • Use when: reading a previously uploaded attachment to extract its content

  • Don't use when: you need the attachment metadata only — use paperclip_list_attachments for id, filename, size

Error Handling:

  • 401: authentication failed → check PAPERCLIP_API_KEY

  • 404: attachment not found → verify UUID with paperclip_list_attachments

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
attachmentIdYesAttachment UUID
response_formatYesOutput format: 'markdown' (default, human-readable) or 'json' (structured)markdown
Behavior4/5

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

Annotations already set readOnlyHint=true, aligning with 'Fetch'. The description adds transparency by detailing the return envelope (attachmentId, contentType, size, contentBase64), response format behavior, and error codes. No contradictions.

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?

Well-structured with clear sections (Args, Returns, Examples, Error Handling). Every sentence serves a purpose, no redundancy. Efficiently conveys all necessary information in a compact format.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Despite no output schema, the description fully explains the return envelope. It covers main usage, differentiates from siblings, and addresses error cases. For a simple 2-param read tool with rich annotations, this is comprehensive.

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%, and the description adds value with an example value for attachmentId ('att_abc123') and clarifies the default and behavior of response_format. This goes beyond the schema by providing contextual examples.

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 'Fetch the content of an attachment by ID' using a specific verb and resource. It distinguishes itself from siblings like paperclip_list_attachments by specifying that it retrieves content, not just metadata.

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

Usage Guidelines5/5

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

Explicitly provides when to use ('when reading a previously uploaded attachment') and when not to use ('need metadata only' → use paperclip_list_attachments). Also includes error handling with actionable advice (check API key, verify UUID).

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/bruhsb/paperclip-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server