Skip to main content
Glama
1msg MCP

1msg MCP

Official
by 1msg

send_reaction

Sends a reaction to a chosen message in a 1msg chat by specifying the chat ID, quoted message ID, and reaction body.

Instructions

Send Reaction

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "send_reaction"
  }
}

Input Schema

NameRequiredDescriptionDefault
bodyNo
phoneNo
chatIdNo
quotedMsgIdNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.2.10
    • addedInput schema / properties / chatId
      Added value: +{
      +  "type": "string"
      +}
  2. First observedv1.2.0

TDQS

D1.3/5.0
Behavior1/5

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

No annotations are supplied, so the description carries the full behavioral burden, yet it discloses nothing about mutation effects, required identifiers, throttling, or delivery semantics. It does not even clarify that this is a write operation that posts a reaction to a message.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The text is short, but that brevity reflects under-specification rather than conciseness. There is no structure, no front-loaded purpose statement, and the single phrase duplicates the name without adding information.

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

Completeness1/5

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

With no annotations, no output schema, 0% parameter coverage, and zero required parameters that nonetheless need identification (message target, chat/phone), the definition is far too thin for a four-parameter messaging mutation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Four parameters exist with 0% schema description coverage, and the description supplies no meaning for any of them. It gives no hint that body is the emoji, that phone/chatId identify the recipient, or whether quotedMsgId is the target message — leaving the agent to guess at required identifiers for a send operation.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose2/5

Does the description clearly state what the tool does and how it differs from similar tools?

"Send Reaction" only restates the tool name and title with no added specificity about which reaction mechanism or channel resource is involved. It does not distinguish this tool from the many sibling send_* tools (send_message, send_sticker, send_button, etc.) that an agent must choose between.

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

Usage Guidelines1/5

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

There is no when-to-use guidance, no when-not-to-use guidance, and no mention of alternatives, despite a crowded sibling set of roughly 20 send_* tools. An agent has no basis in the description for selecting send_reaction over send_message or send_sticker.

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