Skip to main content
Glama
Sign In
Discord Vencord MCP Bridge

Discord Vencord MCP Bridge

by clawdecode
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

discord_get_guild_details

Retrieves comprehensive details and settings for a Discord server or guild, using a guild ID or the active server.

Instructions

Get comprehensive details and settings of a server/guild.

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_get_guild_details"
  }
}

Input Schema

NameRequiredDescriptionDefault
guild_idNoServer ID (defaults to active server).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.9/5.0
Behavior2/5

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

With no annotations provided, the description carries the full disclosure burden. 'Get' implies a read, but nothing states permission requirements, whether the guild must be one the bot is a member of, or how large/heavy the 'comprehensive' payload is. It adds no behavioral context beyond the verb itself.

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?

One short, front-loaded sentence with no filler. It is efficient, though its brevity borders on under-specification rather than tight writing.

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

Completeness3/5

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

For a one-parameter read tool with full schema coverage and no output schema, the description is minimally adequate. It leaves unclear what 'comprehensive details and settings' actually includes, which matters because no return shape is declared.

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 coverage is 100% and the single parameter already documents the 'defaults to active server' fallback. The description contributes no additional parameter semantics, so baseline 3 applies.

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?

A specific verb ('Get') plus a clearly named resource ('details and settings of a server/guild'). It does not, however, distinguish itself from close siblings like discord_get_current_guild or discord_list_guilds, so the agent must infer which one to pick.

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?

There is no explicit when-to-use guidance and no mention of the obvious alternative (discord_get_current_guild for the active server). The default behavior of guild_id is only captured in the schema, not framed as a usage rule.

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