Skip to main content
Glama
discord-mcp

discord-mcp

by zongwei-tang

get_partial_application

Read-only

Retrieves public partial application details for a Discord app or bot by application ID, optionally including guild context.

Instructions

Get Partial Application. [GET /applications/{application_id}/public]

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_partial_application"
  }
}

Input Schema

NameRequiredDescriptionDefault
with_guildNowith guild
application_idYesApplication (app/bot) ID

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, so the safety profile is covered. The description adds only the endpoint path, which weakly implies public unauthenticated access, but it does not say which fields are omitted in the 'partial' response, whether authentication is required, or how it behaves for unknown IDs.

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?

The text is only a title restatement plus a bracketed route, so it is certainly short and front-loaded. However, the brevity comes from under-specification rather than from efficient phrasing — the bracketed HTTP path is the only substantive content.

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?

With no output schema and a resource ('partial application') whose semantics are non-obvious, the description should explain what 'partial' means and what is returned. It leaves that entirely to the agent, making it inadequate for even a simple two-parameter read tool.

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 both parameters are already documented in the schema, and the description adds no meaning beyond it. The opaque 'with_guild' boolean in particular receives no clarification from the description, which is a missed opportunity even at full coverage.

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?

The text 'Get Partial Application' is largely a restatement of the tool name, and 'partial' is never explained — the agent cannot tell what subset of application data this returns versus the sibling get_application. The only added signal is the raw endpoint '/applications/{application_id}/public', which hints at a public read view but does not define a distinguishable purpose.

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 mention of prerequisites, and no comparison to get_application, get_rpc_application, or get_app_directory_app, which all deal with applications. The agent must infer from the endpoint path alone that this is the public/unauthenticated variant.

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