Skip to main content
Glama
discord-self-mcp

discord-self-mcp

by rawnullbyte

discord_channel_info

Retrieve details for a Discord channel, thread, or DM by its channel ID to inspect channel metadata before reading messages or managing the channel.

Instructions

Details of a channel, thread or DM by 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": {
      "channelId": "<channelId>"
    },
    "name": "discord_channel_info"
  }
}

Input Schema

NameRequiredDescriptionDefault
channelIdYesDiscord id (snowflake)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.7/5.0
Behavior2/5

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

With no annotations supplied, the description carries the full disclosure burden, and it only implies a read operation through the word "Details." It does not say whether DM/thread lookups require special permissions or bot access, nor what the returned "details" actually contain, so the agent must discover behavior by calling.

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 sentence with no wasted words and the resource front-loaded. It is terse to the point of under-specification, but nothing in it is 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?

This is a simple one-parameter read tool with no output schema, so the description need not enumerate fields. Still, "Details" is vague enough that the agent cannot anticipate the response shape or confirm that threads and DMs resolve through the same id space, which is the main thing a caller needs here.

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%: channelId is typed as a string with a snowflake pattern and a "Discord id (snowflake)" description. The description's "by id" only restates that, adding no format, resolution, or cross-type (channel vs. thread vs. DM) id nuance beyond the schema.

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

Purpose3/5

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

"Details of a channel, thread or DM by id" names the resource and its variants (channel, thread, DM plus the lookup key), so the domain is unambiguous. However, it uses a noun phrase with no explicit verb ("Details of") and gives no signal distinguishing it from siblings such as discord_guild_info, leaving the retrieval action implied rather than stated.

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?

There is no when-to-use guidance at all: nothing says when to call this versus discord_guild_info or when the id belongs to a thread or DM. The one implicit hint is that any channel-like id works, but no alternatives or exclusions are offered.

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