Skip to main content
Glama
discord-mcp

discord-mcp

by zongwei-tang

modify_guild_member_verification

Updates a Discord server's membership verification settings, including enabled status, description, and required form fields, with an optional audit-log reason.

Instructions

Modify Guild Member Verification. [PATCH /guilds/{guild_id}/member-verification]

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": {
      "guild_id": "<guild_id>"
    },
    "name": "modify_guild_member_verification"
  }
}

Input Schema

NameRequiredDescriptionDefault
reasonNoReason (shown in the audit log)
enabledNoEnabled
guild_idYesServer (guild) ID
bulk_actionNobulk action
descriptionNo
form_fieldsNoform fields

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.5/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false, openWorldHint=true, so safety signalling is covered; the description adds nothing beyond echoing the PATCH endpoint. It does not say whether unlisted fields are preserved or overwritten, whether form_fields replaces the whole list, what permissions are required, or what happens on an unverified guild.

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 short and front-loaded, but the second sentence is API-route trivia rather than agent-relevant information, and the overall brevity leaves the definition under-specified rather than tight. Nothing is padded, but little is earned either.

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 six-parameter mutation tool with no output schema, the description does an inadequate job: it never explains what member verification settings are, what form_fields contain, or what a successful change yields. An agent must open the schema and external API docs to call this correctly.

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 83%, so the schema already documents guild_id, reason, enabled, and description; the description adds no meaning beyond echoing guild_id in the path template. Per the high-coverage baseline, 3 is appropriate, though the ambiguous fields (bulk_action, form_fields) get no clarification anywhere.

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

Purpose3/5

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

The description supplies a verb ('Modify') and a resource ('Guild Member Verification') plus the raw endpoint, but 'Guild Member Verification' is essentially a restatement of the tool name and never explains what this object is (a membership-gate configuration) or what modifying it means. An agent can guess it edits server verification settings, but nothing distinguishes the intent from the sibling get_guild_member_verification beyond the word 'Modify'.

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 at all: no mention of prerequisites, permissions, or when to read (get_guild_member_verification) versus write. The only signal that this is a mutation is the verb and the PATCH path.

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