Skip to main content
Glama

Send a file to a Beeper chat

send_file

Upload a local file up to 500 MB and send it to a chat with an optional caption; confirm the recipient and file before sending.

Instructions

Upload a local file (video, image, audio, document; max 500 MB) and send it to a chat, with an optional caption. This sends a real message on the user's behalf: confirm the recipient and the file first.

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": {
      "chatID": "<chatID>",
      "filePath": "<filePath>"
    },
    "name": "send_file"
  }
}

Input Schema

NameRequiredDescriptionDefault
textNoOptional caption sent with the file
chatIDYesChat ID (or local chat ID) to send to
convertNoVideos only. auto (default): re-encode with ffmpeg, if installed, when the video would play badly on phones (HEVC, 60 fps, full-range color, rotation metadata…). always / never force it.
fileNameNoFile name shown to the recipient (defaults to the local name)
filePathYesAbsolute path of the file to send
replyToMessageIDNoMessage ID to reply to

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.5.1

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false and openWorldHint=true, so the mutation/external-reach profile is known. The description adds useful context beyond that: the 500 MB upload ceiling and the real-message side effect requiring confirmation. It doesn't cover failure behavior, upload progress/timeouts, or required permissions, so it adds value but not rich operational detail.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two sentences, front-loaded with the action, media types and limit, followed by the caution. No redundant wording and every clause carries information. Slightly dense parenthetical but structurally sound.

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?

Annotations cover the safety profile and the schema covers all six parameters, so the description's job is mostly the side-effect warning and the size constraint, both present. The main remaining gap is that with no output schema, nothing tells the agent what a successful send returns (message ID, status), which would matter for follow-up calls.

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?

With 100% schema description coverage, the schema already documents chatID, filePath, fileName, replyToMessageID and the convert enum. The description contributes only the optional-caption mention and the size limit, which lives outside the schema but is not tied to a specific parameter. Baseline 3 is appropriate given the schema does the heavy lifting.

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+resource ('Upload a local file ... and send it to a chat') with concrete scope: supported media types and a 500 MB cap. It is unambiguous about what the tool does, though it doesn't explicitly position itself against the sibling download_attachment or explain that no analogous send-alternative exists.

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 a clear precondition: 'This sends a real message on the user's behalf: confirm the recipient and the file first.' That is genuine when-to-use/confirmation guidance. It stops short of naming alternatives or stating when not to send (e.g., use edit_message for existing messages), so it falls one step below fully explicit routing.

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