Skip to main content
Glama
discord-mcp

discord-mcp

by zongwei-tang

create_application

Creates a Discord application with a required name and optional icon, description, redirect URIs, and related settings.

Instructions

Create Application. [POST /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": {
      "name": "<name>"
    },
    "name": "create_application"
  }
}

Input Schema

NameRequiredDescriptionDefault
iconNo
nameYesName
typeNoType
flagsNoFlags bitfield
team_idNoteam id (ID)
guild_idNo
cover_imageNo
descriptionNo
deeplink_uriNo
redirect_urisNo

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?

The annotations already state that this is a write operation (readOnlyHint=false), open-world, and non-destructive. The description adds only the endpoint path and does not explain permissions, side effects, or what is created beyond the application itself; it does not contradict the annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

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

The description is extremely terse and front-loads the action, but for a 10-parameter creation tool it is under-specified rather than appropriately concise. It omits information an agent needs to use the tool correctly.

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

Completeness1/5

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

For a 10-parameter write tool with no output schema and only generic annotations, the description is far too thin. It omits permissions, application type semantics, parameter relationships, required-field context, and what happens on creation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The description adds no meaning for any of the 10 parameters, and schema description coverage is only 40%. Important fields such as type, flags, team_id, guild_id, and redirect_uris remain ambiguous or undocumented from the description's perspective, so the description does not compensate for the schema gap.

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

Purpose4/5

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

The description explicitly names the action and resource: "Create Application." This is clear and specific, but it does not distinguish the tool from sibling application-related create tools such as create_application_emoji or create_global_application_command.

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 guidance about when to use this tool instead of its siblings, what prerequisites are required, or what kind of application this creates. The intended usage is only implied by the tool 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