Skip to main content
Glama
Sign In
Guildora

Guildora

by az-xx
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Get channel details

get_channel
Read-onlyIdempotent

Retrieve Discord channel, category, thread, or forum post details—topic, slowmode, voice settings, connected members, tags, thread state, missing bot permissions. Supports archived threads by ID/link.

Instructions

Details of one channel, category, thread or forum post: topic, category, slowmode, voice settings and who is connected, forum tags, thread state, and which key permissions the bot lacks there. Works for archived threads by ID or link.

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": {
      "channel": "<channel>"
    },
    "name": "get_channel"
  }
}

Input Schema

NameRequiredDescriptionDefault
guildNoServer ID or name. Optional if DISCORD_GUILD_ID is set or the bot is in one server.
channelYesChannel or thread: ID, <#mention>, link, or name.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.0

TDQS

A4/5.0
Behavior4/5

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

The annotations already declare read-only, idempotent, open-world, non-destructive behavior, so the safety profile is clear. The description adds useful operational context beyond the annotations, notably that it reports slowmode, voice connection state, forum tags, thread state, key missing permissions, and supports archived threads by ID or link. It could still say more about authentication or rate-limit behavior.

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 dense sentence with the primary purpose front-loaded and no filler. Every listed item contributes to understanding what details are returned.

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?

The tool has only two parameters, no nested objects, and no output schema, so the description carries the main burden of explaining return content. It does that well by naming the key fields returned. It is nearly complete, though a brief note on when to prefer this over related lookup tools would fully round it out.

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%, so the accepted channel forms (ID, mention, link, or name) and optional guild parameter are already well documented. The description adds that archived threads can be fetched by ID or link, which is modest extra meaning beyond the schema. Baseline 3 is appropriate because the schema carries most of the parameter semantics.

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 states a specific verb and resource: retrieving details of one channel, category, thread, or forum post. It enumerates concrete fields such as topic, category, slowmode, voice settings, forum tags, thread state, and missing permissions, which clearly distinguishes it from list-oriented siblings like list_channels.

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 "Details of one channel" implies this is the single-resource lookup rather than a listing tool, and archived thread support by ID or link is useful context. However, it does not explicitly say when to use this instead of alternatives such as list_channels or check_access, nor does it state prerequisites or exclusions.

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