Skip to main content
Glama
discord-mcp

discord-mcp

by zongwei-tang

get_guild_discovery_requirements

Read-only

Fetches a Discord server's discovery requirements by guild ID so you can verify eligibility before enabling server discovery.

Instructions

Get Guild Discovery Requirements. [GET /guilds/{guild_id}/discovery-requirements]

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": {
      "guild_id": "<guild_id>"
    },
    "name": "get_guild_discovery_requirements"
  }
}

Input Schema

NameRequiredDescriptionDefault
guild_idYesServer (guild) ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.3/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true, openWorldHint=true and destructiveHint=false, so the safety profile is covered. The description adds nothing beyond the HTTP verb and path — no indication of what is returned, whether an unapproved guild errors out, or what permissions are needed to view discovery requirements.

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 name, but the brevity comes from under-specification rather than efficiency — the bracketed route is the only content beyond the title.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple read tool with annotations and full param coverage this could be adequate, but there is no output schema and the description does not say what a 'discovery requirement' is or what shape the response takes, leaving a real gap for the agent.

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 100% with a single guild_id parameter documented as 'Server (guild) ID', so the schema carries the burden. The description adds no extra meaning (e.g., that the ID must be for a guild eligible for discovery), so baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose2/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description restates the tool name verbatim and appends the raw HTTP route '[GET /guilds/{guild_id}/discovery-requirements]'. It never explains what 'discovery requirements' are (eligibility criteria? thresholds? a checklist?) nor how this differs from the sibling get_guild_discovery_metadata.

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 alternatives such as get_guild_discovery_metadata or modify_guild_discovery_metadata. The agent must infer usage entirely from the 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