Skip to main content
Glama
Sign In
discord-mcp

discord-mcp

by cappyeo
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

guild_change_plan

Read-onlyIdempotent

Create a read-only change plan for a Discord guild to update channels, roles, ordering, and permission overwrites. Preserves existing IDs and omits deletions, requiring approval before apply.

Instructions

Purpose: Inspect an existing guild and create a target-bound, read-only change plan for bounded channel, role, ordering, and permission-overwrite edits.

Safety: Existing IDs are preserved; omitted fields are untouched; creates and deletes are not accepted. The live snapshot, before/after diff, blockers, and approval-bound plan reference must be reviewed before apply.

Returns: {status, plan_id, plan_ref, approval_id, snapshot_id, operations, blockers, risks}.

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>",
      "expected_bot_id": "<expected_bot_id>",
      "request": "<request>",
      "changes": "<changes>"
    },
    "name": "guild_change_plan"
  }
}

Input Schema

NameRequiredDescriptionDefault
changesYesTyped bounded edits translated from the request
requestYesNatural-language explanation of the requested improvement
guild_idYesExplicit existing guild to inspect
expected_bot_idYesExact caller-owned bot ID

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.31.0

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint/idempotentHint/destructiveHint=false, and the description adds real behavioral value beyond them: existing IDs preserved, omitted fields untouched, and creates/deletes rejected. The plan/approval/snapshot binding is also disclosed, giving the agent a clear picture of the non-mutating contract.

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?

Bold Purpose/Safety/Returns headers make it well front-loaded and scannable, with no filler sentences. Mild redundancy: the Returns enumeration repeats what the declared output schema already provides.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a complex nested-object planning tool it covers purpose, the safety contract, and the review-before-apply workflow, and the output schema handles the return shape. The main gap is the absence of routing guidance against the sibling plan/apply/restore tools.

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% and an output schema exists, so the structured fields carry the parameter burden. The description adds only the high-level notion of 'bounded edits' without clarifying any individual parameter's semantics, matching the baseline of 3 when the schema does the heavy lifting.

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 a specific verb and resource: 'Inspect an existing guild and create a target-bound, read-only change plan' scoped to channel, role, ordering, and permission-overwrite edits. This is far more than a name restatement, but it never names or distinguishes itself from sibling planning tools such as guild_blueprint_plan or the adjacent guild_change_apply/guild_change_restore.

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 Safety line implies the sequencing ('must be reviewed before apply'), which hints that this precedes guild_change_apply. However, no sibling is named explicitly and there is no statement of when NOT to use it (e.g., vs. guild_blueprint_plan), so the guidance is implied rather than explicit.

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