Skip to main content
Glama
discord-mcp

discord-mcp

by zongwei-tang

list_user_affinities_v2

Read-only

Lists the Discord users you interact with frequently to help identify close contacts and prioritize conversations.

Instructions

Users you interact with most. [GET /users/@me/affinities/v2/users]

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

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, destructiveHint=false, and openWorldHint=true, so the safety profile is covered. The description adds the endpoint path, which usefully reveals the operation is scoped to the authenticated user via @me and that a v2 versioning scheme applies, but it says nothing about ordering, result size, or whether affinities are scored or ranked.

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 plus an endpoint reference, with the key concept front-loaded and no filler. The bracketed route is somewhat redundant for an agent that cannot use HTTP paths directly, but it is compact rather than wasteful.

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?

With zero parameters and no output schema, the description carries the burden of explaining what comes back, and it only gestures at that with "users you interact with most." It does not state whether results are ordered, capped, paginated, or what fields each affinity entry contains, which matters for a tool whose entire value is the returned ranking.

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 the baseline applies and there is nothing for the description to disambiguate. The absence of parameters is consistent with a simple "who do I interact with" retrieval, and no parameter semantics are missing.

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?

"Users you interact with most" conveys the resource and the ordering concept, but it is a noun phrase rather than a verb+resource statement, so it never explicitly says this is a list/retrieval operation. The scoping to users does distinguish it from list_channel_affinities and list_guild_affinities, which is real value, but the phrasing leaves the agent to infer the action.

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 statement of prerequisites, and no comparison to the affinity siblings (channel, guild) or to get_user_profile. The agent must guess whether this returns IDs, scores, or full profiles, and when this endpoint is preferable to the alternatives.

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