Skip to main content
Glama
discord-mcp

discord-mcp

by zongwei-tang

list_pending_modals

Read-only

Retrieves recently opened bot modal forms and their input fields, so you can inspect pending Discord form requests and respond to the right fields.

Instructions

Forms (modals) bots opened for you recently and their input fields.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_pending_modals"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

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 readOnlyHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is covered. The description adds scoping behavior — modals opened by bots, for you, recently — but does not quantify 'recently', state whether the list is paginated, or explain what happens to modals that expire, so it only modestly exceeds 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 very short and front-loads the resource, but it is a sentence fragment with a missing verb, and its terseness comes partly at the cost of clarity about scope and output. No sentence is wasted, yet the phrase does not earn a high score for structure.

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 zero-parameter read-only list tool this is close to adequate, and the mention of 'input fields' hints at the return shape in the absence of an output schema. However, the undefined recency window and the lack of any indication of ordering, volume, or whether entries are actionable leave real gaps.

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

Parameters4/5

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

The tool takes zero parameters, so the baseline is 4. The description implies there is no filtering input by simply describing a scoped result set; nothing misleading is added.

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?

Names a specific resource — modals (forms) that bots opened for the user — plus the returned detail ('their input fields'), which distinguishes it clearly from the many other list_* siblings. It is a noun phrase fragment rather than a verb+resource statement, and 'recently' leaves the time window undefined, which keeps it below a 5.

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 exclusion, and no reference to what an agent should do next with the returned input fields (e.g., submitting a modal response). The reader must infer the trigger condition entirely.

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