Skip to main content
Glama
discord-mcp

discord-mcp

by zongwei-tang

list_guild_applications

Read-only

Retrieves bots and applications installed in a Discord server, optionally filtered by channel, type, or team inclusion.

Instructions

Bots/apps installed in a server. [GET /guilds/{guild_id}/applications]

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": "list_guild_applications"
  }
}

Input Schema

NameRequiredDescriptionDefault
typeNoType
guild_idYesServer (guild) ID
channel_idNoChannel ID
include_teamNoinclude team

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.5/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 without the description's help. Beyond that, the only added context is the raw endpoint mapping [GET /guilds/{guild_id}/applications], which restates the operation rather than disclosing behavior such as pagination, permissions required, or return shape.

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?

Two short fragments with no filler, so it is certainly not verbose. However, the terseness crosses into under-specification: the endpoint bracket consumes roughly half the text while adding little, and the opening fragment is not a grammatical statement of what the tool returns.

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?

This is a four-parameter list tool with no output schema and no pagination or permission notes; the description covers none of that. An agent would still not know what the response contains or how the optional filters change it, which is a real gap for a filtered-list endpoint.

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%, so all four parameters are already documented in the schema, establishing a baseline of 3. The description adds no meaning beyond that — it says nothing about what type, channel_id, or include_team filter, even though include_team in particular is opaque.

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?

"Bots/apps installed in a server" identifies the resource (guild applications) but is a noun fragment rather than a verb+resource statement, and it never says it lists or returns them. It does not distinguish this from close siblings like list_applications or list_guild_onboarding_allowed_applications, so an agent must infer the difference from names alone.

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?

The description gives no when-to-use guidance, no prerequisites, and no exclusions. There is no hint about when this scope is preferable to list_applications or the onboarding-allowed variant, leaving routing entirely to inference.

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