Skip to main content
Glama
discord-mcp

discord-mcp

by zongwei-tang

list_channel_affinities

Read-only

Retrieve Discord channels ranked by interaction affinity so you can identify where you frequently engage and prioritize active conversations.

Instructions

Channels you interact with most. [GET /users/@me/affinities/channels]

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.1/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered. The description adds the raw endpoint [GET /users/@me/affinities/channels], which usefully confirms the operation is scoped to the authenticated user, but it says nothing about result size, ordering mechanics, or pagination behavior for an openWorldHint tool.

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?

Two short fragments with no filler, and the core statement is front-loaded before the endpoint citation. The bracketed HTTP path is slightly technical noise but earns its place by disambiguating the scope.

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 zero-parameter read tool with annotations covering safety, the definition is close to sufficient, but with no output schema the agent gets no hint about the return shape (channel objects, affinity scores, caps). That gap keeps it at adequate rather than complete.

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?

The tool takes zero parameters, so there is nothing for the description to disambiguate and the baseline applies. The description does not misrepresent the (empty) input contract.

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?

The phrase "Channels you interact with most" identifies the resource and implies an ordering by interaction affinity, but it uses no verb (no "list") and never distinguishes itself from sibling affinity tools such as list_guild_affinities or list_user_affinities_v2. An agent can guess what it returns but must infer that this is the channel-scoped variant from the name alone.

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 guidance on when to call this rather than the guild or user affinity siblings, no prerequisites, and no exclusions. The only context is the endpoint path, which the agent must decode itself.

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