Skip to main content
Glama
discord-mcp

discord-mcp

by zongwei-tang

get_application_command_permissions

Read-only

Retrieves a Discord application command's permission settings in a guild to check which roles and users can access it.

Instructions

Get Application Command Permissions. [GET /applications/{application_id}/guilds/{guild_id}/commands/{command_id}/permissions]

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": {
      "application_id": "<application_id>",
      "guild_id": "<guild_id>",
      "command_id": "<command_id>"
    },
    "name": "get_application_command_permissions"
  }
}

Input Schema

NameRequiredDescriptionDefault
guild_idYesServer (guild) ID
command_idYesApplication command ID
application_idYesApplication (app/bot) ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.6/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. The description adds nothing beyond the endpoint template - no note on authentication requirements, what is returned when permissions are unset, or whether this is a guild-scoped lookup only. With annotations present the bar is lower, but there is virtually no added 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.

Conciseness4/5

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

The definition is extremely short and front-loaded, with the resource name first and the path template second. Nothing is padded, but the endpoint notation is redundant with the tool name for an agent that does not need the REST mapping.

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?

There is no output schema, so the description is the only place to convey what a 'command permissions' object contains (role/user/channel overwrites, permission bits). Given three required IDs and a nested permission payload, the definition is too thin to let an agent reason about the response or follow-up calls.

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%, and the three required parameters (application_id, guild_id, command_id) are each documented in the schema, so the baseline of 3 applies. The description's bracketed path template loosely corroborates the parameter roles but adds no new semantics such as accepted ID formats or snowflake handling.

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?

The description names a specific verb ('Get') and resource ('Application Command Permissions'), so the basic action is identifiable. However, it is essentially a restatement of the tool name plus the raw endpoint, and it gives no signal distinguishing it from siblings such as list_guild_application_command_permissions or modify_application_command_permissions.

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 statement of prerequisites, no mention of when to prefer this over listing permissions or reading a command directly. The only implicit cue is the endpoint, which an agent would have to decode from REST conventions rather than from stated guidance.

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