Skip to main content
Glama
Sign In
Discord Vencord MCP Bridge

Discord Vencord MCP Bridge

by clawdecode
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

discord_get_current_guild

Retrieve details of the currently selected Discord server or guild to identify the active context for messaging, role, or moderation actions.

Instructions

Get details of the Discord server/guild currently selected.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.6/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 behavioral burden. The word "Get" reasonably implies a read-only operation, but the description does not mention what happens if no guild is selected, whether the result is cached, or what the response contains.

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?

The description is a single front-loaded sentence with no unnecessary words. Every part of the sentence contributes to identifying the operation and its scope.

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 simple zero-parameter getter, the description covers the core action, but it omits what details are returned and what happens when no guild is currently selected. With no output schema or annotations, those omissions leave some gaps.

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

Parameters4/5

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

The tool takes zero parameters, so there are no parameter semantics to document. A baseline score of 4 is appropriate for a zero-parameter tool.

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 uses a clear verb ("Get") and resource ("details of the Discord server/guild currently selected"). It implicitly distinguishes itself from guild-listing and guild-detail-by-id siblings by emphasizing the currently selected guild, though it does not name an alternative explicitly.

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 phrase "currently selected" implies when the tool is appropriate, namely when the agent needs the active guild context rather than an arbitrary guild. However, there is no explicit guidance about when not to use it or which sibling to use instead.

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