Skip to main content
Glama
iCloud MCP Server Apple

iCloud MCP Server Apple

React To Message

react-message
Destructive

Sends a tapback reaction (love, like, dislike, laugh, emphasis, or question) to a specified Messages chat, enabling quick responses in Apple Messages conversations.

Instructions

Send a tapback reaction (love, like, dislike, laugh, emphasis, question)

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": {
      "chatId": "<chatId>",
      "type": "<type>"
    },
    "name": "react-message"
  }
}

Input Schema

NameRequiredDescriptionDefault
typeYesReaction type
chatIdYesChat ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv2.1.1

TDQS

C2.9/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=false, destructiveHint=true, idempotentHint=false and openWorldHint=true, so the safety profile is covered. The description adds nothing beyond that: it does not say whether a new reaction replaces an existing one, whether repeating the call toggles or stacks reactions, or how failures (unknown chat) surface.

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?

A single short phrase with zero filler, front-loading the verb and resource. It is a fragment rather than a full sentence, but nothing is wasted.

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?

This is a mutating, destructive-flagged, open-world write tool, yet the description gives no context on effect, reversibility, or targeting. Most notably it claims to 'react to a message' while the schema exposes only chatId and type, with no message identifier — the description never clarifies how the target message is determined, which is a material ambiguity for an agent.

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 both parameters and the reaction enum are fully documented in the schema; the baseline is 3. The description's parenthetical reaction list merely restates the enum and adds no new meaning, and it is silent on the semantics of chatId.

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 ('Send') and resource ('tapback reaction') and enumerates the allowed reaction types, so an agent immediately knows what it does. It does not differentiate from siblings like send-message, which also write to a chat, leaving selection partially to inference.

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 when-to-use guidance, no exclusions, and no mention of the sibling send-message tool or when a reaction is preferable to a reply. It also omits prerequisites such as the chat needing to exist or the agent needing an established session.

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