Skip to main content
Glama

Local MCP

by com.local-mcp
OverviewDiscussionsAdmin

WhatsApp Send File

whatsapp_send_file
Destructive

Sends a file attachment to a WhatsApp chat. The chat_id MUST come from a previous whatsapp_list_chats call — never fabricate IDs. file_path must be an absolute path to a local file. This is a write operation: the first call (confirm=false) returns a preview without sending; set confirm=true to actually send.

Input Schema

NameRequiredDescriptionDefault
accountNoWhich linked WhatsApp account to use: its label or id from whatsapp_list_accounts. Leave it out to use the default account.
captionNoOptional caption text to accompany the file
chat_idYesChat ID from whatsapp_list_chats
confirmNoMust be true to actually send. Without it, returns a preview.
rememberNoWith confirm: true, also stop asking for this kind of action from now on. Only when the person said so ("don't ask again"). The person can revoke it in LMCP or with set_always_allowed.
file_pathYesAbsolute path to the local file to send

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / remember
      Added value: +{
+  "description": "With confirm: true, also stop asking for this kind of action from now on. Only when the person said so (\"don't ask again\"). The person can revoke it in LMCP or with set_always_allowed.",
+  "type": "boolean"
+}
  2. Changed1 schema field changed
    • addedInput schema / properties / account
      Added value: +{
+  "description": "Which linked WhatsApp account to use: its label or id from whatsapp_list_accounts. Leave it out to use the default account.",
+  "type": "string"
+}
  3. Added
  4. Removed
  5. First observed

TDQS

A4.7/5.0
Behavior5/5

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

Annotations declare destructiveHint=true and readOnlyHint=false, and the description adds the crucial operational detail the annotations cannot convey: the first call with confirm=false only returns a preview and nothing is sent until confirm=true. It also discloses the ID-provenance constraint, which is real behavioral risk information.

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 short sentences with zero filler, ordered by importance: what it does, then the hard constraint on IDs, then the safety-critical confirm flow. Every clause carries operational weight.

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?

With an output schema present and annotations covering the risk profile, the description supplies exactly the missing pieces an agent needs: ID provenance, absolute path requirement, and the preview-before-send protocol. Nothing required to invoke it correctly is absent.

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 the baseline is 3; the description earns an increment by explaining that chat_id is a foreign key from whatsapp_list_chats and that file_path is an absolute local path, and by explaining the two-phase meaning of confirm. account, caption and remember are left entirely to their 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?

States a specific verb and resource — 'Sends a file attachment to a WhatsApp chat' — which separates it from the text and poll siblings (whatsapp_send_message, whatsapp_send_poll) without opening any schema. The two-step preview/send behavior is named in the same breath.

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 strong preconditions: chat_id must come from a prior whatsapp_list_chats call and must never be fabricated, and file_path must be absolute. It does not explicitly route between this tool and whatsapp_send_message for text, but the attachment framing makes the choice obvious.

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

All Local MCP toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources