Skip to main content
Glama
discord-mcp

discord-mcp

by zongwei-tang

list_guild_affinities

Read-only

List the Discord servers you interact with most, ranked by affinity, to identify your top guilds.

Instructions

Servers you interact with most. [GET /users/@me/affinities/guilds]

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_guild_affinities"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.1/5.0
Behavior2/5

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

Annotations already establish readOnly, non-destructive, open-world behavior, so the safety profile is covered. Beyond that the description adds only the REST endpoint path; it never says how results are ordered, whether the list is bounded or paginated, or roughly what an affinity entry looks like — notable gaps for a ranking endpoint with 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?

Two short, front-loaded fragments with no wasted words. The bracketed HTTP path is developer-facing noise that does not help an agent decide or invoke, but it costs little.

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, no-output-schema read tool the safety side is fully covered by annotations, but the description leaves the return shape (what an affinity record carries, how many entries, ordering direction) entirely undefined. Adding one clause about the ranking and result size would make it 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 and the schema confirms an empty property set, so there is nothing for the description to disambiguate and it does not mislead about inputs. Baseline for a parameterless tool applies.

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?

The fragment 'Servers you interact with most' identifies both the resource (servers/guilds) and the ranking criterion (affinity/interaction frequency), which is more specific than the bare name alone. It does not name a verb, so the list operation is only conveyed by the name, and it does not distinguish itself from related siblings such as list_channel_affinities or list_user_affinities_v2. Still, an agent can tell this returns a ranked guild affinity list.

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 prerequisite, and no mention of the closely related affinity endpoints. An agent must infer that this is the guild-scoped variant of affinity listing purely from the tool name.

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