Skip to main content
Glama
Sign In
time-messenger-mcp-server

time-messenger-mcp-server

by BarredEwe
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

get_reactions

Retrieve all emoji reactions for a specified message post ID, showing which users reacted and with which emoji.

Instructions

List all emoji reactions on a message

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": {
      "post_id": "<post_id>"
    },
    "name": "get_reactions"
  }
}

Input Schema

NameRequiredDescriptionDefault
post_idYesPost ID of the message

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.4.0

TDQS

A3.7/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full burden. The word 'all' usefully signals that no emoji/user filtering is applied, but it says nothing about permissions, ordering, pagination, or whether results are capped, which an agent would want before calling.

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 short sentence with the resource and scope front-loaded; there is no filler or redundant restatement of the tool name.

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 simple one-parameter read tool this is minimally sufficient, but with no output schema the description could have said what a reaction record contains (emoji, user, timestamp) and whether the list is paginated.

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 100% for the single post_id parameter, so the baseline is 3. The phrase 'on a message' reinforces that post_id identifies the target message but adds no format or validation detail beyond the schema.

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

Purpose5/5

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

States a specific verb (List) and resource (emoji reactions) scoped to a single message, which cleanly separates it from the add_reaction and remove_reaction siblings without needing to name them.

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 implied rather than stated: an agent can infer this is the read counterpart to add_reaction/remove_reaction, but the description never says when to choose it or mentions any alternatives or prerequisites such as channel membership.

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