Skip to main content
Glama
iCloud MCP Server Apple

iCloud MCP Server Apple

Send Message

send-message
Destructive

Send an iMessage or SMS to a phone number or email with an optional file attachment; delivery is immediate and cannot be recalled.

Instructions

Sends an iMessage or SMS to a phone number or email handle, with an optional file attachment. The message is delivered as soon as the tool runs; there is no draft step and no recall.

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>",
      "body": "<body>"
    },
    "name": "send-message"
  }
}

Input Schema

NameRequiredDescriptionDefault
toYesRecipient phone number (with country code) or email
bodyYesMessage content
fileNoPath to file attachment (optional)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv2.1.1

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true, idempotentHint=false and openWorldHint=true, so the irreversibility profile is partly given. The description reinforces this usefully with "delivered as soon as the tool runs; there is no draft step and no recall," but adds nothing about failure modes, invalid recipients, or delivery confirmation.

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 tight sentences with no filler; the core action comes first and the irreversibility warning follows. Nothing is wasted, though a routing clause would have added value at the same length.

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?

For a three-parameter messaging tool with no output schema, the description covers what is sent, to whom, and that it is irreversible on invocation. Remaining gaps, such as recipient validation and per-message error behavior, are minor at this complexity.

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 description coverage is 100%, so all three parameters are already documented at the schema level. The description restates the recipient forms and optional attachment without adding format or syntax detail, so it only matches rather than extends the schema.

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 (sends) and resource (iMessage/SMS) plus recipient forms and optional attachment, which is clear. It does not explicitly differentiate itself from the sibling send-email, so an agent must infer the channel split.

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?

"iMessage or SMS to a phone number or email handle" implicitly frames usage, and the no-draft/no-recall note signals this is for immediate dispatch. There is no explicit when-not guidance or named alternative such as send-email for email delivery.

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