Skip to main content
Glama
discord-mcp

discord-mcp

by zongwei-tang

list_friend_suggestions

Read-only

Retrieve suggested friends for a Discord account so you can review potential connections and decide who to add.

Instructions

Friend suggestions. [GET /friend-suggestions]

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.8/5.0
Behavior2/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 by structured data. The description adds nothing beyond that – no indication of result ordering, pagination, whether suggestions depend on mutual friends, or how many are returned – so with the bar lowered by annotations it still contributes essentially zero behavioral context.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

It is short and front-loads the resource name, but it reads as a label fragment rather than a definition – the endpoint bracket is the only added information. There is no wasted wording, yet the brevity comes from under-specification rather than efficiency.

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?

The tool is simple: no parameters, no nested objects, no output schema, and annotations cover the read-only/open-world profile. Minimum viable for such a tool, but an agent still lacks any statement of what a suggestion list contains or when it should be fetched.

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 is empty, so there is no parameter meaning to convey; baseline 4 applies. Nothing in the description contradicts 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?

"Friend suggestions" plus the endpoint hint [GET /friend-suggestions] identifies the resource and implies retrieval, but the verb is only implied by the tool name and there is no differentiation from siblings such as list_friends or remove_friend_suggestion. An agent can guess what it returns but gets no statement of what a 'suggestion' actually is.

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 exclusions, and no mention of the adjacent tools (list_friends, add_friend, remove_friend_suggestion) that an agent would otherwise have to compare schemas to choose between. The only contextual cue is the bare HTTP path.

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