Skip to main content
Glama
discord-mcp

discord-mcp

by zongwei-tang

get_channel_info

Read-only

Retrieve readable details for a Discord channel, thread, or DM, including type, server, topic, recipients, and last activity, to understand context before acting.

Instructions

Readable info about a channel/thread/DM (type, server, topic, recipients, last activity).

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>"
    },
    "name": "get_channel_info"
  }
}

Input Schema

NameRequiredDescriptionDefault
channel_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/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 contributes by naming the information returned (type, server, topic, recipients, last activity), but says nothing about permission requirements or behavior for inaccessible/unknown channels. Given annotation coverage, a 3 is appropriate.

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?

One compact sentence, front-loaded with the core action and the resource, with the field list as a parenthetical. Nothing is redundant, though the compression leaves the reader with no structural cue about scope or alternatives.

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 single-parameter read-only tool with annotations covering the safety profile and no output schema, the description is largely sufficient: it identifies the resource and previews the returned fields. The main residual gap is channel-type/permission behavior, which is minor at this complexity.

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 0% and the single parameter is documented only as a string, so the description must carry the load. It does add meaning by indicating channel_id may identify a channel, thread, or DM, but gives no ID format or examples, so an agent still has to guess what a valid value looks like.

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 ('readable info') and resource ('channel/thread/DM') and enumerates the returned fields, so the agent knows exactly what it gets back. It does not differentiate itself from closely named siblings such as get_channel or get_dm_channel, which an agent could easily mistake for the same operation.

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, no prerequisites, and no mention of any alternative. The description never explains why an agent would pick this over get_channel or get_dm_channel, leaving selection to inference from the name alone.

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