Skip to main content
Glama
Sign In
Discord MCP - Discord server management MCP for AI agents

Discord MCP - Discord server management MCP for AI agents

by OrygnsCode
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Get thread

get_thread
Read-only

Retrieve a Discord thread’s settings, current state, and counts by thread name or ID to inspect or manage the thread; optionally scope the lookup to a specific guild.

Instructions

One thread's settings, state, and counts.

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": {
      "thread": "<thread>"
    },
    "name": "get_thread"
  }
}

Input Schema

NameRequiredDescriptionDefault
guildNoGuild (server) name or ID. Omit to use the default guild.
threadYesThread name or ID.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.4.2
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
  2. Changed1 schema field changedv1.3.0
    • removedInput schema / additionalProperties
      Removed value: -false
  3. First observedv1.0.2

TDQS

C2.5/5.0
Behavior2/5

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

The readOnlyHint annotation already establishes this is a non-mutating read, so the description's main obligation is to add context. It contributes only a vague enumeration ('settings, state, and counts') and says nothing about permissions required to view a thread, behavior for inaccessible or archived threads, or shape/size of the result.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

It is short and front-loaded, which is good, but it is a bare noun phrase with no verb, so the brevity comes at the cost of clarity rather than being efficient compression. A single added verb would have made it both short and unambiguous.

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

Completeness2/5

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

For a two-parameter read tool with no output schema, the description should at least clarify what 'state' and 'counts' mean (member count, message count, archived/locked status) and how lookups fail. None of that is present, so an agent knows only the roughest outline of the return.

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 both the guild and thread parameters documented as 'name or ID' including the default-guild fallback. The description adds no further meaning about parameter behavior, so the baseline 3 applies.

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

Purpose3/5

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

The fragment 'One thread's settings, state, and counts' identifies the resource (a single thread) and roughly what is returned, so an agent can tell it is a single-thread read rather than a mutation like update_thread or a membership listing. However, there is no verb and no explicit statement that it fetches/retrieves, leaving the purpose implied rather than stated.

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?

No when-to-use guidance appears: nothing says to prefer this over get_channel or get_server_overview, and nothing states prerequisites such as needing a thread ID vs a name or what happens when the thread is missing. The only usage signal is the schema's note that guild can be omitted to use the default.

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