Skip to main content
Glama
discord-mcp

discord-mcp

by zongwei-tang

discord_api_request

Call any Discord HTTP API route as your own account when no dedicated tool exists. Send the method, path, query, body, and files to reach unsupported endpoints.

Instructions

Escape hatch: call any Discord HTTP API route as your account (path relative to /api/v9, e.g. "/users/@me/billing/subscriptions"). Use when no dedicated tool exists.

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": {
      "method": "<method>",
      "path": "<path>"
    },
    "name": "discord_api_request"
  }
}

Input Schema

NameRequiredDescriptionDefault
bodyNo
pathYes
filesNoFiles to attach (each: path, url or data_base64)
queryNo
methodYes
reasonNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior3/5

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

The annotations already disclose that this is not read-only, is open-world, and is flagged non-destructive, and the description usefully adds that requests execute "as your account" under an authenticated session. What it omits matters, though: the method enum includes DELETE, and nothing warns that escape-hatch mutations can be irreversible, that Discord rate limits apply, or that changes made through arbitrary routes bypass the safety rails of dedicated tools — a tension with the destructiveHint=false annotation that goes unaddressed.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

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

Two sentences, both front-loaded, with the escape-hatch framing first and the routing rule last. No filler or repetition of the tool name.

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?

There is no output schema and six parameters with nested file objects, so the description should do more. It covers the most important thing (the base path and route format) but leaves payload construction, file attachment mode, and the audit-log "reason" parameter entirely to inference.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is only 17%, so the schema does not carry the load. The description only explains the "path" parameter (relative to /api/v9, with an example); it says nothing about body, query, files, or the "reason" parameter, so an agent must guess at the request payload shape and cannot tell that "reason" is presumably an audit-log justification.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description uses a specific verb and resource ("call any Discord HTTP API route as your account") and frames the tool as an "Escape hatch," which makes its role distinct from the many dedicated siblings. The example path ("/users/@me/billing/subscriptions") and the base-route convention ("relative to /api/v9") make the scope concrete.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

"Use when no dedicated tool exists" gives an explicit trigger condition for choosing this tool over the sibling operations. It stops short of a when-not-to-use list or naming specific alternatives, but the routing rule is clear enough to act on.

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