Skip to main content
Glama

whatsapp_send_file

Send files directly through WhatsApp. Transfer documents, images, and other files to your contacts without needing to open the app.

Instructions

Send a file via WhatsApp

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • server.js:88-88 (registration)
    Tool registration stub for 'whatsapp_send_file' – this is a minimal MCP stub that lists the tool so Glama can detect it; the real implementation is in a native binary not present in this codebase.
    ["whatsapp_send_file", "Send a file via WhatsApp"],
  • Generic stub handler for all tools – returns a placeholder message. The real handler logic for whatsapp_send_file lives in the native binary (not present in this repository).
    server.tool(name, desc, {}, async () => ({
      content: [{ type: "text", text: "This is an inspection stub. Install Local MCP: npx -y local-mcp@latest setup" }],
    }));
  • Empty schema (no input parameters defined) for the tool registration stub.
    server.tool(name, desc, {}, async () => ({
Behavior2/5

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

No annotations provided; description lacks details on behavior (e.g., file source, size limits, return value). Insufficient for a mutation tool.

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?

Single sentence, no fluff. Efficient for the limited information provided.

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

Completeness2/5

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

With no parameters, annotations, or output schema, the description is too brief. It doesn't explain how to specify the file, making it incomplete for an agent.

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?

No parameters exist (0 params, 100% schema coverage), so baseline 4. Description adds no param info, but none is needed.

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?

Clear verb+resource ('Send a file') and distinct from sibling tools like whatsapp_send_message, which sends text.

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?

No guidance on when to use this tool versus alternatives, nor any context about prerequisites or file specification.

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/lanchuske/local-mcp-releases'

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