Skip to main content
Glama
Sign In
Guildora

Guildora

by az-xx
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Recent activity across channels

recent_activity
Read-onlyIdempotent

Shows which Discord channels and threads had messages since a time, newest first, with message/people counts and latest message, so you can scan server activity without opening channels one by one.

Instructions

Shows which channels and threads had messages from people since a time ("24h" by default, or "7d", an ISO date), newest first, with how many messages and people and the latest message (include_bots adds bot activity). Use it to see what is going on without opening channels one by one; then read_messages.

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

Input Schema

NameRequiredDescriptionDefault
guildNoServer ID or name. Optional if DISCORD_GUILD_ID is set or the bot is in one server.
limitNoMax channels (1-50, default 20).
scopeNoLimit to a category, channel, forum or thread (ID or name). Default: the whole server.
sinceNoHow far back: "2h", "24h" (default), "7d", or an ISO date.
cursorNonext_cursor from a previous call.
include_botsNoAlso count bot and webhook messages (default false: people only).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.0

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already establish readOnly, idempotent, non-destructive and open-world, so the bar is lower; the description still adds real substance by specifying the default window (24h), the newest-first ordering, the per-channel aggregation (message and people counts), the latest message, and the bot-exclusion default. Pagination behavior and the cursor contract are left to the schema.

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?

Two sentences, front-loaded with the return shape and ending with the usage/next-step cue. Dense with parentheticals but every clause carries information; nothing redundant.

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?

All six parameters are optional and fully documented in the schema, and with no output schema the description properly describes the return shape (channels, counts, latest message, ordering). The only gaps are pagination/cursor mention and no explicit contrast with the nearest sibling.

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 coverage is 100%, so the schema already documents every parameter including since, include_bots and cursor. The description adds only a default restatement for since and a gloss on include_bots, which the schema itself covers; it contributes no syntax or format detail beyond the structured fields. 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?

States a specific verb and resource ('Shows which channels and threads had messages') plus the aggregation shape (message/people counts, latest message, newest first). It is clearly distinct from read_messages and list_channels, which it references, though it does not distinguish itself from get_new_messages or list_unanswered.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives an explicit use case ('see what is going on without opening channels one by one') and a concrete next step ('then read_messages'). It stops short of saying when to prefer the sibling get_new_messages instead, so the routing guidance is one-directional.

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