Skip to main content
Glama
discord-mcp

discord-mcp

by zongwei-tang

submit_modal

Fill and submit a Discord bot form (modal) by mapping each input custom_id to text or select values; uses the recent modal by default when no ID is provided.

Instructions

Fill in and submit a bot form (modal). values maps each input custom_id to text (or a list for selects). Defaults to the most recent modal.

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": {
      "values": "<values>"
    },
    "name": "submit_modal"
  }
}

Input Schema

NameRequiredDescriptionDefault
valuesYes
modal_idNo
wait_secondsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already declare this is a non-read-only, open-world, non-destructive operation, so the safety profile is known. The description adds the useful defaulting behavior (most recent modal) but says nothing about what submission triggers, whether a bot response is awaited, or what happens on failure, which is significant for an open-world mutation.

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?

Three short sentences, front-loaded with the action and followed by the parameter mapping rule, with no filler. The terseness costs some needed detail, but nothing written is wasted.

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?

For a non-read-only, open-world tool with no output schema and zero schema description coverage, the definition is thin: wait_seconds semantics, the result of submission, and error conditions (no open modal, stale custom_ids) are all absent. The nested values object is handled well, but the surrounding behavior an agent needs is not.

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 coverage is 0%, so the description must carry the parameter burden and it partly does: it explains values as a custom_id-to-text map, including the list form for selects, which the bare additionalProperties schema cannot convey. It also implies modal_id via "defaults to the most recent modal". wait_seconds is never mentioned anywhere, leaving one of three parameters fully undocumented.

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?

"Fill in and submit a bot form (modal)" gives a specific verb pair and a specific resource, which is far clearer than any sibling name in the catalog. It stops short of 5 only because it doesn't contrast itself with any alternative path for interacting with a bot, but the action is unambiguous.

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

Usage Guidelines3/5

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

Usage is implied rather than stated: an agent can infer it should call this when a modal is open and needs completing. There is no explicit guidance on prerequisites (where the custom_ids come from, what happens if no modal is open) or on when not to use it.

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