Skip to main content
Glama
discord-mcp

discord-mcp

by zongwei-tang

get_soundboard_sound_guild

Read-only

Retrieve the guild linked to a soundboard sound by sound ID and guild ID to confirm which server owns it.

Instructions

Get Soundboard Sound Guild. [GET /soundboard-sounds/{sound_id}/guild/{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": {
      "sound_id": "<sound_id>",
      "guild_id": "<guild_id>"
    },
    "name": "get_soundboard_sound_guild"
  }
}

Input Schema

NameRequiredDescriptionDefault
guild_idYesServer (guild) ID
sound_idYesSoundboard sound ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.1/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 safety is covered structurally. The description adds nothing beyond the URL pattern — no note on permissions, cross-guild visibility rules, or error behavior (e.g. whether a 404 occurs when the sound is not available to that guild). With annotations carrying the safety profile, the remaining behavioral value here is near zero.

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, with no filler sentences. However, the single sentence is largely redundant with the tool name, and the bracket-notation endpoint is a raw path fragment rather than agent-facing language.

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 two-parameter read with full schema coverage and clear annotations, the structured fields do most of the work, but the description still leaves the core question unanswered: what does this return and how does it differ from the sibling get_guild_soundboard_sound. Complexity is low, yet the definition is thinner than the tool warrants.

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 description coverage is 100%: both sound_id ("Soundboard sound ID") and guild_id ("Server (guild) ID") are already documented in the schema. The description adds no syntax, format, or constraint detail, 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?

"Get Soundboard Sound Guild" only restates the tool name, and the appended REST path [GET /soundboard-sounds/{sound_id}/guild/{guild_id}] is the only thing hinting at what is actually retrieved (the guild associated with a sound). It never states in prose whether the result is a guild object, a routing/eligibility check, or a cross-server lookup, and it does not distinguish itself from the near-identically named sibling get_guild_soundboard_sound.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines1/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 when-not-to-use, and no mention of the closely related siblings (get_guild_soundboard_sound, list_guild_soundboard_sounds). The agent must guess from the endpoint path alone which of the several soundboard GET tools to call.

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