Skip to main content
Glama
discord-mcp

discord-mcp

by zongwei-tang

get_application

Read-only

Retrieves details for a Discord application or bot by its application ID, letting you look up bot profile and configuration data before managing or inspecting it.

Instructions

Get Application. [GET /applications/{application_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": {
      "application_id": "<application_id>"
    },
    "name": "get_application"
  }
}

Input Schema

NameRequiredDescriptionDefault
application_idYesApplication (app/bot) ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.4/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 fully covered elsewhere. The description's only added detail is the HTTP route, which tells the agent little about behavior such as error handling for unknown IDs or what the returned object contains.

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 terse fragments with no wasted words, but the brevity reflects under-specification rather than disciplined economy. The most useful element, the endpoint, is relegated to a bracket.

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

Completeness3/5

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

For a single-parameter read tool with full schema coverage, complete annotations, and no output schema, the definition is minimally sufficient to invoke correctly. It stops short of anything that would help the agent interpret results or handle failures.

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% for the single required application_id, and the schema already describes it as "Application (app/bot) ID". The description adds no format, source, or validation detail beyond that, so the baseline of 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 Application" merely restates the tool name, and the bracketed endpoint adds only that it maps to GET /applications/{application_id}. It does nothing to distinguish this from siblings such as get_partial_application or get_rpc_application, which an agent would need to choose between.

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 guidance on when to use this versus the many other application-related retrieval tools, nor any prerequisites or exclusions. The verb "Get" implies a read, but nothing more is conveyed.

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