Skip to main content
Glama
Sign In
Discord Vencord MCP Bridge

Discord Vencord MCP Bridge

by clawdecode
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

discord_get_channel_info

Retrieve metadata for a specific Discord channel by ID, including details needed to route messages, inspect settings, or verify channel context.

Instructions

Get metadata for a specific Discord channel by ID.

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

Input Schema

NameRequiredDescriptionDefault
channel_idNoDiscord channel ID.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.5/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. 'Get metadata' strongly implies a read-only operation, but the description does not disclose permission requirements, failure behavior, or what metadata is returned; for a low-risk read tool this is minimally adequate.

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?

A single, front-loaded sentence with no wasted words. It states the action, resource, lookup key, and expected return category compactly.

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 one-parameter read tool with full schema coverage and no output schema, the description covers the essential call semantics. It leaves return-value and permission expectations unstated, which is acceptable but not rich.

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 the single parameter is documented in the schema. The description only restates that lookup is by channel ID, adding no syntax or semantic detail beyond the schema.

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: 'Get metadata' for a 'Discord channel' identified 'by ID.' This makes it distinguishable from siblings like discord_get_current_channel and discord_list_guild_channels, though it does not explicitly name those alternatives.

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?

Usage is implied by 'by ID' – use when a channel ID is known – but the description does not explicitly say when to choose this over discord_get_current_channel or discord_list_guild_channels.

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