Skip to main content
Glama
Sign In
discord-mcp

discord-mcp

by cappyeo
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

permissions_member_access_report

Read-onlyIdempotent

Reports a member's effective view, send, and manage access across selected guild channels, applying Discord role and overwrite rules.

Instructions

Purpose: Report one member’s effective view/send/manage access across a bounded set of guild channels.

Safety: Read-only. It reuses Discord role and overwrite semantics, preserves unknown results for incomplete payloads, and does not infer access for ambiguous threads.

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": {
      "guild_id": "<guild_id>",
      "user_id": "<user_id>"
    },
    "name": "permissions_member_access_report"
  }
}

Input Schema

NameRequiredDescriptionDefault
user_idYesMember whose perspective is evaluated
guild_idYesGuild to inspect
channel_idsNoOptional bounded channel selection; omit for all returned guild channels

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.31.0

TDQS

A3.7/5.0
Behavior5/5

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

Annotations already declare read-only, idempotent, and non-destructive behavior, and the description adds substantial context beyond that: it states the tool reuses Discord role and overwrite semantics, preserves unknown results for incomplete payloads, and refuses to infer access for ambiguous threads. These disclosures directly shape how an agent should interpret the report and are non-obvious from the schema and annotations alone.

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?

Two short, labeled sections front-load purpose and safety with no filler. Every sentence carries useful information.

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?

With an output schema covering return values and annotations covering safety, the description supplies purpose and behavioral nuances. The main gap is the absence of routing guidance relative to sibling permission tools, which slightly reduces completeness.

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 all three parameters are documented in the schema. The description adds no parameter-level syntax, format, or constraint detail beyond what the schema already provides, so the baseline 3 applies.

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?

The description names a specific verb ('Report') and resource ('one member’s effective view/send/manage access across a bounded set of guild channels'), making the operation precise. However, it does not explicitly differentiate from siblings like permissions_explain or permissions_audit_channel, so it falls short of a 5.

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 or when-not-to-use guidance is provided. The description does not name alternatives such as permissions_explain or permissions_audit_channel, leaving the agent to infer routing from the tool name and purpose 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