Skip to main content
Glama
discord-mcp

discord-mcp

by zongwei-tang

remove_application_tester

Destructive

Removes a user from a Discord application's tester allowlist using the application ID and user ID.

Instructions

Remove Application Tester. [DELETE /oauth2/applications/{application_id}/allowlist/{user_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>",
      "user_id": "<user_id>"
    },
    "name": "remove_application_tester"
  }
}

Input Schema

NameRequiredDescriptionDefault
user_idYesUser ID
application_idYesApplication (app/bot) ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/5.0
Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare destructiveHint=true, readOnlyHint=false and openWorldHint=true, so the risky nature of the call is known without the description. The endpoint string adds a small amount of real context by showing the resource lives under /oauth2/applications/{application_id}/allowlist, but the description says nothing about what happens on success, whether the removal is idempotent, or how errors are returned when the user is not an allowlisted tester.

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?

Two compact elements: a plain-language action statement followed by the underlying HTTP route. The action is front-loaded and there is no filler, though the bracketed endpoint is closer to reference metadata than explanatory prose.

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?

With only two required scalar parameters, no output schema, and annotations that already flag the destructive/write nature, the definition is close to sufficient. It falls short on authorization requirements and failure behavior, which matter for a destructive allowlist mutation, but nothing an agent strictly needs to select and invoke the tool is missing.

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%, with both application_id and user_id documented in the schema, so the description carries no extra burden. It adds no meaning beyond the schema for either parameter, which is the expected baseline when the schema is complete.

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 gives a specific verb+resource pair ('Remove Application Tester') and pins down the exact operation via the endpoint '[DELETE /oauth2/applications/{application_id}/allowlist/{user_id}]', which tells an agent this deletes a user from an application's tester allowlist. It does not explicitly contrast with the sibling add_application_tester, but the inverse operation is unambiguous from the naming.

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 or when-not-to-use guidance, no mention of prerequisites (e.g. owner/admin permission on the application), and no reference to alternatives such as add_application_tester. The agent must infer usage entirely from the name and endpoint.

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