Skip to main content
Glama

Activity report

discord_activity_report
Read-only

Generates a Discord server activity report for the last N days, showing messages, active people, quiet channels, and forum post status so admins can spot inactive areas and stale posts.

Instructions

How the server (or one category) is being used over the last N days: messages and active people per channel, quiet channels, and for forums the open posts, posts per tag and posts idle for N+ days.

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": "discord_activity_report"
  }
}

Input Schema

NameRequiredDescriptionDefault
daysNo
idle_daysNoForum posts idle this long count as stale
category_idNoOnly this category

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so safety posture is covered. The description adds useful behavior context by enumerating what the report surfaces (quiet channels, stale forum posts), but says nothing about output volume, aggregation level, permission requirements, or how 'active people' is computed — all material for interpreting an analytics result.

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

Conciseness4/5

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

A single dense sentence that front-loads the primary scope ('how the server... is being used over the last N days') before the metric list. Every clause maps to a real output dimension, so nothing is padding, though the nested parenthetical and trailing forum clause make it slightly harder to parse at a glance.

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 no output schema, the description carries the burden of describing return values, and it does so reasonably by listing the metrics produced. Gaps remain around response shape (flat table vs. per-channel sections), whether empty/quiet channels are always included, and any permission prerequisites — meaningful for an open-world analytics call.

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?

All three parameters get meaning from the description text: `days` as the reporting window, `idle_days` as the staleness cutoff for forum posts ('posts idle for N+ days'), and `category_id` as the 'one category' scoping option. It goes beyond the schema by tying each knob to a specific reported metric, though it does not restate the 1–90 / 1–365 bounds already in the schema.

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 concrete analytical product — per-channel message and active-person counts, quiet channels, and forum post/tag/staleness metrics over the last N days — which is far more specific than the title 'Activity report'. It implicitly separates this read-only analytics tool from the surrounding `discord_admin_*` mutation siblings, but never states that contrast explicitly.

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?

Scope is implied by 'over the last N days' and 'the server (or one category)', so an agent can infer this is a retrospective usage summary. However, there is no statement of when to prefer this over sibling tools, no prerequisites (e.g., needing message-history permission), and no exclusions for very large servers.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.