Skip to main content
Glama
discord-mcp

discord-mcp

by zongwei-tang

get_discovery_slug

Read-only

Retrieves the discovery slug for a Discord server by guild ID via GET /discovery/{guild_id}, giving assistants the identifier needed for discovery-based server lookups.

Instructions

Get Discovery Slug. [GET /discovery/{guild_id}]

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

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, destructiveHint=false, and openWorldHint=true, so the safety profile is covered structurally. The description adds nothing beyond the HTTP verb and path—no note on permissions required for discovery endpoints, no indication of when a slug may be absent, and no hint at the response shape despite there being 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.

Conciseness3/5

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

It is brief and front-loaded, so there is no wasted prose. However, the second fragment (the REST path) conveys little an agent can act on and reads like generated filler rather than purposeful structure.

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?

With no output schema, the description is the only place an agent could learn what a discovery slug looks like, what it is used for, or what happens when discovery is not enabled for the guild—none of which is provided. For a simple one-parameter read the gap is survivable but still substantial.

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% and the single guild_id parameter is well documented as 'Server (guild) ID', so the schema carries the load. The description only echoes the parameter placement in the URL template and adds no new meaning, which is the expected baseline.

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?

'Get Discovery Slug' essentially restates the tool name with an undefined term; it never explains what a 'discovery slug' is or how it differs from siblings like get_guild_discovery_metadata or get_guild_discovery_requirements. The bracketed REST route [GET /discovery/{guild_id}] adds a small amount of resource context but no conceptual clarity.

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 when another discovery endpoint would be the right call instead. The only usage information is the implicit HTTP route, which an agent must interpret on its own.

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