Skip to main content
Glama

send_file

Encrypt and send a file up to 25 MiB to a named device, room, or recipient list, with an optional caption for real-time messaging between AI agent sessions.

Instructions

Encrypt and send a file (at most 25 MiB) with an optional caption.

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": {
      "to": "<to>",
      "path": "<path>"
    },
    "name": "send_file"
  }
}

Input Schema

NameRequiredDescriptionDefault
toYesname@device, #room, *, or a list
pathYes
captionNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.1/5.0
Behavior2/5

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

With no annotations supplied, the description carries the full burden and discloses only encryption and a size cap. It says nothing about delivery semantics, whether recipients must be known peers/rooms, whether sends are queued or persisted, or what happens when the file exceeds the limit.

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 with no filler; the size constraint sits in parentheses where it is easy to scan.

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

Completeness3/5

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

For a 3-parameter tool with no annotations and no output schema, this is minimal but workable: send + encrypt + size cap + optional caption. The critical gaps are the meaning/format of 'path' and any error behavior for oversized files.

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 only 33%, but the description does add that the caption is optional and that the file payload is bounded at 25 MiB. However, 'path' is left entirely unexplained — no indication of whether it is a local absolute path, a workspace-relative path, or a previously uploaded identifier — which is the key ambiguity for this tool.

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 gives a specific verb pair and resource ('Encrypt and send a file') plus a meaningful bound ('at most 25 MiB'), which is more than a restatement of the name. It implicitly distinguishes itself from the plain 'send' sibling by being file-specific, but never explicitly says so.

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

Usage Guidelines2/5

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

There is no when-to-use or when-not guidance, and no mention of the 'send' sibling as the alternative for non-file content. The only selection-relevant information is the 25 MiB ceiling, which is a constraint rather than usage direction.

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