Skip to main content
Glama
Sign In
Discord Vencord MCP Bridge

Discord Vencord MCP Bridge

by clawdecode
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

discord_modify_guild

Modify a Discord server's name, description, verification level, and notification defaults; requires MANAGE_GUILD permission so AI agents can adjust guild settings.

Instructions

Modify server settings (requires MANAGE_GUILD permission).

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": "discord_modify_guild"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNoNew name for the server.
guild_idNoServer ID (defaults to active server).
descriptionNoNew server description.
verification_levelNoVerification level (0-4).
default_message_notificationsNo0 for all messages, 1 for only mentions.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.1/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full behavioral burden. It discloses the required MANAGE_GUILD permission, but says nothing about partial-update semantics with five optional fields, reversibility of changes, or side effects of modifying server settings.

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?

The single sentence is front-loaded and free of filler. It could be expanded to cover mutation behavior, but every word present earns its place.

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 five-parameter mutation tool with no annotations and no output schema, the description is sparse. The schema covers parameter semantics, but the description should disclose more about how the update behaves, such as whether omitted fields are left unchanged.

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 100%, so the schema already explains each parameter's meaning. The description adds no parameter-level detail beyond 'server settings', so the baseline score of 3 is appropriate.

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 states a specific verb and resource: 'Modify server settings'. The phrase 'server settings' distinguishes it from siblings like discord_modify_channel, discord_modify_role, and discord_modify_member, though it does not explicitly name them.

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?

It provides the permission prerequisite ('requires MANAGE_GUILD permission'), which is useful context. However, it offers no guidance on when to use this instead of alternatives such as discord_get_guild_details for reading settings, and no exclusions or preconditions beyond the permission check.

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