Skip to main content
Glama
Sign In

Aiguild

by me.aiguild
OverviewDiscussionsAdmin

Preview a Discord server on AiGuild

preview_discord_server
Read-onlyIdempotent

Use this when the user wants to create, set up or reorganize a Discord server and a structure (categories, channels, roles) has been designed with them. Do not use it for general Discord questions, moderation help, or requests that do not involve setting up a server. It returns a preview of the structure and a link to aiguild.me; nothing is created or changed on Discord. On aiguild.me the user signs in with Discord, reviews or edits the structure and applies it to a server they manage; existing channels are kept by default.

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": {
      "server_name": "<server_name>",
      "language": "<language>",
      "categories": "<categories>"
    },
    "name": "preview_discord_server"
  }
}

Input Schema

NameRequiredDescriptionDefault
rolesNoRoles from the most powerful to the least. Do not include @everyone.
systemsNoBot systems AiGuild sets up when the structure is applied. Welcome and levels are on by default; basic AutoMod protection (invite links, mention raids) is always switched on.
languageYesLanguage of the server: channel names and the bot's messages. Use en for a language not listed.
categoriesYesCategories in display order, each with its channels. A typical server has 4 to 8 categories and 15 to 40 channels.
descriptionNoOne or two sentences about the community.
server_nameYesName of the Discord server, e.g. Survival Haven.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Beyond the readOnly/destructive annotations, it discloses the return value (a preview of the structure plus an aiguild.me link), that nothing is written to Discord, that the user must sign in with Discord and confirm/apply manually, and that existing channels are preserved by default. These are substantive behavioral facts an agent needs and that no annotation or schema conveys.

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?

Three sentences, front-loaded with the selection condition, then exclusions, then behavioral consequences. No filler, though the opening sentence is somewhat long and the workflow sentence could be tightened without losing information.

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

Completeness5/5

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

For a tool with a deep nested schema, no output schema and no siblings, the description covers selection, exclusions, what is returned, and what happens to the user's server afterward. Nothing essential is missing for correct invocation.

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% with rich nested documentation (roles, categories, channels, access, language), so the schema already carries parameter meaning. The description references categories, channels and roles only in passing and adds no format or constraint detail beyond the schema, which is the correct baseline of 3.

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

Purpose5/5

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

The description names a specific verb (preview) and resource (a designed Discord server structure: categories, channels, roles) and states the precondition that a structure has already been designed with the user. It also explicitly says nothing is created or changed on Discord, so an agent cannot mistake it for an apply/deploy tool.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives explicit when-to-use (user wants to create, set up or reorganize a server and a structure exists) and explicit when-not-to-use (general Discord questions, moderation help, requests that do not involve setting up a server). It also states the post-call workflow on aiguild.me, so the agent knows what happens after invocation.

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

All Aiguild toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources