Skip to main content
Glama
Sign In
Guildora

Guildora

by az-xx
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Find conversations waiting for staff

list_unanswered
Read-onlyIdempotent

Identify unanswered Discord channels, tickets, threads, and forum posts where the latest message is from a non-staff member, sorted by longest wait, to prioritize replies.

Instructions

Finds channels, tickets, threads and forum posts where the latest message from a person is not from staff, i.e. someone is waiting for a reply; sorted by longest wait. Staff = members with staff_roles, or by default anyone with Administrator, Manage Server, Manage Channels, Manage Messages or Timeout Members. Bot messages are ignored unless bot_replies_count is true.

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_unanswered"
  }
}

Input Schema

NameRequiredDescriptionDefault
guildNoServer ID or name. Optional if DISCORD_GUILD_ID is set or the bot is in one server.
limitNoMax results (1-50, default 25).
scopeNoLimit to a category, channel, forum or thread (ID or name). Default: the whole server.
sinceNoOnly conversations active within this window (default "30d").
cursorNonext_cursor from a previous call (continues the scan).
min_waitNoOnly those waiting at least this long, e.g. "2h". Default: any.
staff_rolesNoRoles whose members count as staff (IDs or names).
bot_replies_countNoTreat messages from bots as answers (default false).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.0

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnlyHint, idempotentHint, destructiveHint=false), so the description's job is to add semantics, which it does: it defines what counts as staff (staff_roles, or the five default permissions), discloses that bot messages are excluded unless bot_replies_count is true, and states the longest-wait ordering. It omits any mention of scan/pagination behavior or result shape, which keeps it from a 5.

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?

It is a single dense sentence set with the core predicate front-loaded and no filler. The semicolon-chained clauses are slightly run-on, but every clause (staff definition, bot carve-out) carries decision-relevant information, so nothing is wasted.

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?

For an 8-parameter, zero-required, read-only discovery tool with no output schema, the description supplies the conceptual model (staff, waiting, bot handling, ordering) an agent needs to interpret results. The only gap is return-value expectations and how cursor-based continuation relates to the wait ordering, which the schema handles only partially.

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?

Schema coverage is 100%, so the baseline is 3; the description earns an extra point because it explains the interaction between staff_roles and the default permission set, and clarifies that bot_replies_count flips the bot-exclusion rule rather than merely 'treating bots as answers'. These are non-obvious behaviors not derivable from the schema text alone.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb ('Finds') plus the exact resource set (channels, tickets, threads, forum posts) and a precise predicate: the latest message from a person is not from staff. The ordering rule ('sorted by longest wait') is included, so the agent knows both what is returned and how it is ranked, which distinguishes it from siblings like search_messages or recent_activity.

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?

The description makes the use case unambiguous — surfacing conversations where someone is awaiting a reply — and explains the staff resolution rule that determines inclusion. It stops short of naming a sibling alternative or an explicit when-not-to-use condition, so no credit for routing guidance, but the context is clear enough to select the tool confidently.

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