Skip to main content
Glama
discord-mcp

discord-mcp

by zongwei-tang

get_directory_entry

Read-only

Retrieves a directory entry from a Discord channel using the channel ID and entity ID, so you can resolve or inspect a linked entity.

Instructions

Get Directory Entry. [GET /channels/{channel_id}/directory-entry/{entity_id}]

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>",
      "entity_id": "<entity_id>"
    },
    "name": "get_directory_entry"
  }
}

Input Schema

NameRequiredDescriptionDefault
entity_idYesEntity ID
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.6/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 safety and external-API nature are covered structurally. The description adds nothing beyond that: no auth requirements, no not-found/error behavior, no note that this reads live remote state.

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 very short and front-loaded with zero padding, which is good, but the brevity reflects under-specification rather than disciplined editing. The bracketed REST path adds mild implementation context that is not useful to an agent selecting the tool.

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 two-parameter read with full schema coverage and no output schema, the definition is minimally viable. It is missing what an entry object represents and what happens when the entity is absent, gaps that matter somewhat given the openWorldHint.

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 required parameters documented (entity_id, channel_id including channel-type enumeration in prose). The description contributes only the endpoint path templating, which is marginal beyond the schema, 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?

"Get Directory Entry" essentially restates the tool name, but the appended endpoint [GET /channels/{channel_id}/directory-entry/{entity_id}] reveals that it is a single-resource fetch keyed by channel and entity. It is distinguishable from list_directory_entries and search_directory_entries by the singular resource, though the description never explicitly contrasts them.

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 at all: nothing says to use this when the entity ID is already known, nor that list/search siblings should be used to discover an ID. The agent must infer the retrieval-vs-discovery split entirely from the names.

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