Skip to main content
Glama
Sendmux

Sendmux Email Inbox API + Sending

Official

Upload Attachment

mailbox_upload_attachment

Upload an attachment file for use when sending an email. Supports local file path, presigned URL, or inline base64 as a last resort.

Instructions

Use this before sending a mailbox attachment. Cheapest mode: file_path on local stdio MCP reads the user-approved local file without putting bytes in model context. Hosted or shell-capable agents should set presign_upload_url=true with filename, content_type, and size_bytes, then PUT the file to the returned short-lived URL promptly and send the returned blob_id. Inline content_base64 is a last resort for tiny agent-authored files only and is capped at 32 KiB decoded.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
filenameYesFilename to use when sending the uploaded attachment.
file_pathNoLocal file path for stdio MCP only. The path must be inside a client-declared MCP root; hosted MCP rejects it.
mailbox_idNoMailbox public ID when the credential can access more than one mailbox.
size_bytesNoExact byte size required when presign_upload_url=true.
content_typeNoMIME type to store with the upload, for example application/pdf.application/octet-stream
content_base64NoLast-resort inline base64 for tiny agent-authored files only. Decoded content must be at most 32 KiB; use file_path or presign_upload_url for real files.
presign_upload_urlNoWhen true, return a short-lived signed PUT URL instead of reading bytes. Provide size_bytes and upload with a shell/client promptly.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior4/5

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

Description adds behavioral context beyond annotations: cheapest mode, last resort, 32 KiB cap, and that presign returns a short-lived URL for prompt upload. No contradictions with annotations.

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?

Three sentences, front-loaded with purpose, no wasted words. Each sentence adds essential information about the three modes.

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?

Description is thorough given the tool complexity (7 params, 1 required). Covers all upload modes, constraints, and workflow steps. Output schema exists, so return values are documented elsewhere.

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%, so baseline is 3. Description adds meaningful usage context for each parameter (e.g., 'cheapest mode', 'last resort, tiny agent-authored files only'), exceeding schema descriptions.

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?

Clearly states the tool is for uploading an attachment before sending a mailbox message. Distinguishes three modes (file_path, presign_upload_url, content_base64) with specific use cases, which differentiates it from siblings.

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?

Provides explicit guidance on when to use each mode: file_path for local stdio, presign for hosted/shell, content_base64 only as last resort. Implies context but doesn't explicitly exclude alternative tools.

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/Sendmux/sendmux-sdk'

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