Skip to main content
Glama

discord_update_membership_screening

Configure membership screening forms to require new members to review rules and answer questions before joining a Discord server.

Instructions

Update the membership screening form: set a description and rules/questions that new members must agree to before joining.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
guild_idYes
descriptionNoWelcome message shown at the top of the screening form.
form_fieldsNoList of rules/questions. Each item has: label (the rule title), values (array of rule lines), required (boolean).

Implementation Reference

  • Implementation of the `discord_update_membership_screening` tool handler, which fetches current screening state and patches it with new description/fields.
    case "discord_update_membership_screening": {
      const guildId = validateId(args.guild_id, "guild_id");
      const current = await discord.rest.get(`/guilds/${guildId}/member-verification`) as Record<string, unknown>;
      const body: Record<string, unknown> = { version: current.version };
      if (args.description !== undefined) body.description = args.description as string;
      if (args.form_fields !== undefined) {
        const fields = args.form_fields as { label: string; values: string[]; required?: boolean }[];
        body.form_fields = fields.map((f) => ({
          field_type: "TERMS",
          label: f.label,
          values: f.values,
          required: f.required ?? true,
        }));
      }
      const updated = await discord.rest.patch(`/guilds/${guildId}/member-verification`, { body });
      return { content: [{ type: "text", text: `✅ Membership screening updated.\n${JSON.stringify(updated, null, 2)}` }] };
    }
  • Input schema definition for the `discord_update_membership_screening` tool.
    {
      name: "discord_update_membership_screening",
      description: "Update the membership screening form: set a description and rules/questions that new members must agree to before joining.",
      inputSchema: {
        type: "object",
        properties: {
          guild_id: { type: "string" },
          description: { type: "string", description: "Welcome message shown at the top of the screening form." },
          form_fields: {
            type: "array",
            description: "List of rules/questions. Each item has: label (the rule title), values (array of rule lines), required (boolean).",
            items: {
              type: "object",
              properties: {
                label: { type: "string", description: "Title/question for this field." },
                values: { type: "array", items: { type: "string" }, description: "Array of rule lines or answer options." },
                required: { type: "boolean", description: "Whether this field is required (default true)." },
              },
              required: ["label", "values"],
            },
          },
        },
        required: ["guild_id"],
      },
    },
Behavior2/5

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

No annotations are provided, so the description carries full burden. It implies a mutation ('Update') but doesn't disclose behavioral traits like required permissions, whether changes are reversible, rate limits, or error conditions. The description is minimal and lacks operational context.

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?

Single sentence, front-loaded with the core action, zero waste. Every word contributes directly to explaining the tool's function efficiently.

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 mutation tool with no annotations and no output schema, the description is incomplete. It doesn't cover permissions, side effects, response format, or error handling. Given the complexity of updating a screening form, more context is needed for safe and effective use.

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 67% (2 of 3 parameters have descriptions). The description adds that 'description' is a welcome message and 'form_fields' are rules/questions for new members, which aligns with schema descriptions but doesn't provide significant extra meaning. Baseline 3 is appropriate given moderate schema coverage.

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 clearly states the action ('Update') and resource ('membership screening form'), specifying what gets updated: description and rules/questions. It distinguishes from siblings like discord_get_membership_screening (read vs. write) but doesn't explicitly contrast with other update tools like discord_update_forum_post.

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?

No guidance on when to use this tool versus alternatives. It doesn't mention prerequisites (e.g., admin permissions), when not to use it, or how it differs from other configuration tools. The description is purely functional without contextual advice.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/PaSympa/discord-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server