Skip to main content
Glama
discord-mcp

discord-mcp

by zongwei-tang

get_directory_counts

Read-only

Retrieve the number of directory entries for a Discord channel by channel ID.

Instructions

Get Directory Counts. [GET /channels/{channel_id}/directory-entries/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": {
      "channel_id": "<channel_id>"
    },
    "name": "get_directory_counts"
  }
}

Input Schema

NameRequiredDescriptionDefault
channel_idYesChannel ID (text, voice, thread, forum or DM channel)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.3/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=true, so the safety profile is covered. The description contributes nothing beyond that: no indication of what the counts represent, whether they are aggregated or per-entry-type, or whether the channel must be a directory channel.

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-loads the name, but the terseness comes at the cost of content rather than being efficient. Two fragments with no explanatory sentence leave the core semantics unexplained.

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 simple read tool with one well-described parameter and full annotations, the remaining gap is the return semantics: "counts" is ambiguous and there is no output schema to compensate. The definition should state at minimum what is counted relative to a channel's directory entries.

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?

There is only one parameter and schema description coverage is 100%, so the schema already fully documents channel_id and its accepted channel types. The description adds no additional meaning about the parameter, so the baseline of 3 applies.

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

Purpose2/5

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

"Get Directory Counts" essentially restates the tool name; the only added information is the REST endpoint, which reveals that the counts belong to directory entries within a channel. It never says what is being counted (entries per type? total members?) and does nothing to distinguish it from siblings like list_directory_entries or get_directory_entry.

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 when-to-use guidance, no prerequisite notes, and no mention of alternatives such as list_directory_entries for retrieving the entries themselves. The agent must infer usage from the name and endpoint alone.

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