Skip to main content
Glama
Sign In
Capes

Capes

by Dipeshpal
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

discord_add_reaction

Add a Unicode or custom (name:id) emoji reaction to a Discord message using its channel ID, message ID, and emoji.

Instructions

React to a message. emoji is a unicode emoji (👍) or a custom emoji as name:id.

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": {
      "channel_id": "<channel_id>",
      "message_id": "<message_id>",
      "emoji": "<emoji>"
    },
    "name": "discord_add_reaction"
  }
}

Input Schema

NameRequiredDescriptionDefault
emojiYes
channel_idYesChannel ID (a thread ID also works)
message_idYesMessage ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false, and openWorldHint=true, so the safety profile is covered. The description adds the emoji input format but says nothing about permission requirements or behavior on duplicate reactions, so it only modestly exceeds the structured data.

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?

Two short sentences, front-loaded with the action and followed immediately by the non-obvious parameter format. No filler.

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 simple three-parameter reaction tool with no output schema, the description covers the action and the tricky emoji format. Only minor gaps remain (permissions, duplicate handling) that annotations partially offset.

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 67%; the emoji parameter has no schema description, but the description compensates by defining valid syntax (unicode emoji or custom name:id), which is the most error-prone input. channel_id and message_id are already documented in 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 and resource: 'React to a message.' This naturally distinguishes it from the sibling discord_remove_reaction and discord_list_reactions, though it never names an alternative to make the contrast explicit.

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, prerequisites, or routing to alternatives is given. The agent must infer from the name alone that this adds rather than removes or lists reactions.

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

Deploy Server

Other Tools