Skip to main content
Glama
discord-mcp

discord-mcp

by zongwei-tang

get_message_request_details

Read-only

Retrieves supplemental details such as mutual servers for pending Discord message requests by channel ID, helping assess unknown senders before accepting.

Instructions

Get extra details (e.g. mutual servers) for pending message requests. [GET /users/@me/message-requests/supplemental-data]

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": "get_message_request_details"
  }
}

Input Schema

NameRequiredDescriptionDefault
channel_idsNoChannel IDs

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=true, so the safety profile is covered. The description adds that the data is supplemental and scoped to pending requests, but says nothing about pagination, rate limits, or what happens for channel_ids that are not pending — useful context that is missing given no output schema.

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 front-loaded sentence with the key qualifier ('pending message requests') stated before the example, plus the endpoint in brackets for traceability. No wasted prose, though the bracketed route is arguably redundant filler.

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 read-only tool with annotations covering safety, the description is adequate but thin: with no output schema, the return shape is only hinted at via one example ('e.g. mutual servers'), and the relationship of the results to the channel_ids input is left unexplained.

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?

Only one parameter exists and schema description coverage is 100%, so the baseline is 3. The description does not clarify what channel_ids should contain (pending request channels only? batch limits?), adding no meaning beyond the schema's 'Channel IDs'.

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?

Specific verb ('Get') plus resource ('extra details ... for pending message requests') with a concrete example ('mutual servers') and the backing endpoint. It is clearly distinguishable from the sibling mutations accept_message_request and reject_message_request. It stops short of naming a sibling alternative, which keeps it from a 5.

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 by 'pending message requests' and 'extra details', suggesting a follow-up enrichment call, but there is no explicit statement of when to call this versus the sibling message-request tools (accept/reject/batch_reject) or under what preconditions (e.g. only after listing requests).

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