Skip to main content
Glama
discord-self-mcp

discord-self-mcp

by rawnullbyte

discord_edit_guild

Rename a Discord server or update its description by providing the guild ID; requires Manage Server permission.

Instructions

Rename the server or change its description. Requires Manage Server.

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": {
      "guildId": "<guildId>"
    },
    "name": "discord_edit_guild"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNo
reasonNo
guildIdYesDiscord id (snowflake)
descriptionNo

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?

No annotations are provided, so the description carries the full burden. It does disclose the required permission, which is genuine behavioral context, but it omits that the reason parameter surfaces in the audit log, that description can be set to null to clear it, and whether the change is reversible.

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?

Two short sentences with zero waste; the action is front-loaded and the permission constraint follows immediately. Nothing is padded or redundant.

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, no output schema, and 25% parameter coverage, the description is too thin — it leaves the audit-log reason and the null-clearing semantics of description undocumented. An agent could invoke it but would not understand the side effects.

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

Parameters2/5

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

Schema coverage is only 25%, so the description must compensate, yet it only names 'name' and 'description' and says nothing about the required guildId target or the 'reason' parameter (which has no schema description at all). The most opaque parameter is left entirely unexplained, so the description adds little beyond the schema's type constraints.

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?

States specific verbs (rename, change description) applied to a specific resource (the server/guild), which clearly separates it from siblings like discord_edit_channel or discord_edit_role. It could be slightly sharper by naming the guild explicitly as the target object rather than the colloquial 'server'.

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?

The prerequisite 'Requires Manage Server' tells the agent a permission gate exists, which is useful. However, there is no guidance on when to prefer this over related tools (e.g., discord_guild_info for reading settings) and no note about what happens if the bot lacks the permission.

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