Skip to main content
Glama

send_message

Send an outbound message from an authorised inbox (0 credits when sending to internal @botmail.work recipients via the Agent Handoffs)

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": {
      "inboxId": "<inboxId>",
      "to": "<to>",
      "subject": "<subject>",
      "bodyText": "<bodyText>",
      "operationId": "<operationId>"
    },
    "name": "send_message"
  }
}

Input Schema

NameRequiredDescriptionDefault
toYesRecipient email (internal @botmail.work addresses route for 0 credits)
inboxIdYesInbox to send from
subjectYes
bodyTextYes
operationIdYesIdempotency key (required)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Beyond the annotations (readOnly=false, openWorld=true, destructive=false), the description adds two useful behavioral facts: sending requires an authorised inbox, and internal @botmail.work recipients cost 0 credits via the Agent Handoffs. It leaves delivery timing, threading, and rate limits unstated.

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?

One sentence, front-loaded with the action and its scope, with the credit exception in a tight parenthetical. Nothing is wasted and no qualifying information is buried.

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 mutation tool with five required parameters and no output schema, the description covers who can send and what it costs but omits what the response contains, whether idempotent replays return the same message, and whether the send is immediate. Adequate but with clear gaps.

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 60% — to, inboxId, and operationId are documented in the schema. The description's internal-recipient routing note duplicates the `to` parameter description rather than adding new semantics, and says nothing about subject/bodyText constraints or what the operationId idempotency key guarantees.

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 ('Send an outbound message') and scopes it to an authorised inbox, which is enough to identify it. It does not differentiate itself from the sibling reply_to_message, which is the most likely confusion for an agent choosing between the two.

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

Usage Guidelines3/5

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

Usage is only implied: 'outbound message from an authorised inbox' hints at the prerequisite and the credit note hints at the internal-recipient case. There is no explicit when-to-use-this-vs-reply_to_message guidance and no stated preconditions beyond 'authorised'.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources