Skip to main content
Glama
discord-mcp

discord-mcp

by zongwei-tang

list_application_testers

Read-only

Retrieve the allowlisted testers for a Discord application by application ID, so you can review who is authorized to test it.

Instructions

List Application Testers. [GET /oauth2/applications/{application_id}/allowlist]

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": "list_application_testers"
  }
}

Input Schema

NameRequiredDescriptionDefault
application_idYesApplication (app/bot) ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.9/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true, openWorldHint=true, and destructiveHint=false, so the safety profile is covered. The description adds only the HTTP route, which implicitly reveals the tool reads the OAuth2 allowlist, but says nothing about pagination, result shape, or what happens for an app with no testers.

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 very short and front-loaded with the tool name, which is good, but the bracketed HTTP route is low-value metadata for an agent and the whole definition is under-informative rather than tight. Nothing is padded, yet little is conveyed.

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 one-parameter read-only listing tool with annotations and full schema coverage, the minimal description is barely sufficient. An agent can call it correctly, but it lacks any note on output format or scoping that would make the definition self-sufficient.

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?

There is a single parameter with 100% schema description coverage ('Application (app/bot) ID'), so the schema already carries the meaning. The description adds nothing about application_id, which is acceptable at this coverage level but earns no bonus.

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 names a specific verb and resource — listing the testers of an application — which is unambiguous on its own. It does not explicitly contrast with add_application_tester or remove_application_tester, but the 'List' prefix distinguishes it well enough from those mutation siblings.

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 stated prerequisites (e.g., needing an application_id or ownership rights), and no mention of alternatives such as remove_application_tester. The agent must infer the context from the verb alone.

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