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

List event subscriptions

list_event_subscriptions
Read-only

Retrieves active event subscriptions and their buffer sizes, helping AI agents inspect current Discord event monitoring and manage subscription capacity.

Instructions

Active event subscriptions and their buffer sizes.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_event_subscriptions"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.4.2
    • addedInput schema / $schema
      Added value: +"https://json-schema.org/draft/2020-12/schema"
  2. First observedv1.0.2

TDQS

B3.4/5.0
Behavior3/5

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

readOnlyHint=true already tells the agent this is a safe read with no side effects. The description adds genuinely useful context beyond the annotation: the result is filtered to active subscriptions and each carries a buffer size. It does not say anything about ordering, volume, or whether inactive subscriptions are retrievable elsewhere, so the added value is modest.

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 a single short fragment with zero padding, so nothing is wasted, but it is under-specified rather than tightly structured: there is no leading verb and no sentence conveying what the agent gets back in a callable form. Brevity here reflects minimal content rather than efficient editing.

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 zero-parameter, read-only lister with no output schema, the description covers the essentials: what is returned and one property of the payload. It leaves undefined what an 'event subscription' is in this system and whether results are paginated or capped, which an agent would need to interpret the output correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool takes no parameters, so there is nothing for the description to disambiguate; the empty schema is fully self-explanatory. Baseline 4 for a zero-parameter tool applies, with no parameter-related gaps created by the description.

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 fragment names a specific resource (event subscriptions) and narrows scope to active ones plus their buffer sizes, which is more than a restatement of the name. It lacks a verb ('List' is only implied) and does not explicitly distinguish itself from sibling listers such as list_events, but the resource is distinctive enough that an agent can identify what it returns.

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?

Usage is only implied: the word 'Active' hints this is a diagnostic/inspection call, but there is no statement of when to call it, when not to, or what alternative exists if the agent wanted historical or inactive subscriptions. For a zero-parameter read tool the implied usage is acceptable, but nothing is made explicit.

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