Skip to main content
Glama
Sign In
Guildora

Guildora

by az-xx
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Get new messages

get_new_messages
Read-onlyIdempotent

Fetch messages that arrived since your last call across a Discord server, channel, category, or forum, oldest first, then pass the returned cursor to retrieve only newer messages.

Instructions

Returns messages that arrived across the server (or a channel, category or forum) since your last call, oldest first, from what Guildora received live during this session. Pass the returned next_cursor next time to get only newer ones. only_mentions keeps messages that mention or reply to the bot. For older history use recent_activity or 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": "get_new_messages"
  }
}

Input Schema

NameRequiredDescriptionDefault
guildNoServer ID or name. Optional if DISCORD_GUILD_ID is set or the bot is in one server.
limitNoMax messages (1-200, default 50).
scopeNoOnly this channel, thread, category or forum (ID or name).
cursorNonext_cursor from the previous call. Default: everything since startup.
include_botsNoInclude bot and webhook messages (default false).
only_mentionsNoOnly messages that mention or reply to the bot.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.0

TDQS

A4.6/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 bar is lower, and the description still adds real context: results come only 'from what Guildora received live during this session', which is a substantive scope limitation an agent would otherwise assume away. It does not discuss cursor expiry, gaps while offline, or rate limits, so it stops short of full behavioral disclosure.

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?

Four tight sentences, front-loaded with what the tool returns and the incremental nature, then the cursor mechanic, then the mentions filter, then the routing alternative. No restatement of the name or title and no filler.

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 a six-parameter read tool with no output schema, the description covers the essential mental model: session-live scope, cursor chaining, and mention filtering, plus a pointer to siblings for history. It stops short of describing the returned message shape or what happens if a cursor is stale, which leaves a modest gap given there is no output schema.

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 baseline would be 3; the description earns above that by explaining the cursor round-trip ('pass the returned next_cursor next time') and the parenthetical scope mapping for 'scope' (channel, category or forum). It adds little for limit, guild, or include_bots beyond what the schema already says.

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 and resource ('Returns messages'), the scope it covers (server, channel, category or forum), the ordering ('oldest first'), and the temporal window ('since your last call'). It also names the siblings it is not (recent_activity, read_messages), so an agent can distinguish it without opening any schema.

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

Usage Guidelines5/5

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

Gives an explicit alternative for the main confusion case: 'For older history use recent_activity or read_messages.' It also states the incremental workflow ('Pass the returned next_cursor next time to get only newer ones') and the only_mentions narrowing, so the selection conditions are spelled out rather than implied.

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