Skip to main content
Glama
discord-mcp

discord-mcp

by zongwei-tang

get_app_directory_app

Read-only

Retrieve a Discord application's directory profile by application ID, optionally with locale and localized fields. Use it to look up app or bot information from Discord's application directory.

Instructions

Get Application Directory Application. [GET /application-directory-static/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_app_directory_app"
  }
}

Input Schema

NameRequiredDescriptionDefault
localeNolocale
nocacheNonocache
application_idYesApplication (app/bot) ID
with_localizationsNowith localizations

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?

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=true, and the description adds nothing beyond restating "GET." It does not mention that results come from a static/external directory, whether the response is cached or how nocache affects behavior, or what happens for an unknown application_id — all of which would have earned credit beyond 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.

Conciseness3/5

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

It is short and front-loaded, so there is no bloat, but the first sentence is redundant with the tool name and the second is just a route template. Brevity here reflects under-specification rather than disciplined editing.

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 tool with no output schema, the description should at least sketch what a directory application record contains or how localizations are returned. With four parameters and an external open-world data source, the minimal name-plus-route text leaves the agent without enough context to call it confidently.

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% (locale, nocache, application_id, with_localizations all documented), so the schema does the heavy lifting and the baseline is 3. The description contributes no additional parameter meaning — notably it says nothing about how locale, nocache, or with_localizations alter the returned payload.

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 Directory Application" is a near-verbatim restatement of the tool name (get_app_directory_app), not an independent explanation of purpose. The bracketed HTTP route (GET /application-directory-static/applications/{application_id}) does imply it retrieves a single directory application by ID, which lifts it slightly above pure tautology, but the description never says what a directory application is or how it differs from get_application or search_app_directory.

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 at all: nothing distinguishes this from search_app_directory (discovery), get_application (likely app lookup), or list_app_directory_categories. The agent must infer from the name and HTTP path alone that this is the single-item fetch for the directory resource.

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