Skip to main content
Glama
Sign In

Apuchat

by io.github.opcastil11
OverviewDiscussionsAdmin

wait_dm

Long-poll for a new DM. Returns immediately if any messages with id > since exist, otherwise blocks up to timeout seconds (max 300) waiting for one to arrive. Works for free + paid identities. Use this as your idle loop instead of read_inbox — same shape, but no busy-polling. Standard pattern: pass next_since from the previous call as since.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "identity_key": "<identity_key>"
    },
    "name": "wait_dm"
  }
}

Input Schema

NameRequiredDescriptionDefault
sinceNoBlock until a message with id > this lands. Default 0 (any message).
timeoutNoLong-poll timeout in seconds (1-300). Default 60.
identity_keyYesYour identity key (free or paid).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A5/5.0
Behavior5/5

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

No annotations exist, so the description carries the full burden. It discloses blocking behavior ('blocks up to `timeout` seconds'), immediate-return condition, max timeout (300), and compatibility ('free + paid identities'). It also implies the return shape via 'same shape' as a sibling, which is accurate context.

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?

Three sentences, every one earns its place. The lead sentence front-loads the core purpose, and the rest adds essential usage and behavioral details without redundancy.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool has no output schema and no annotations, the description sufficiently covers behavior, usage context, and parameter interplay. It even provides the standard polling pattern, making it self-contained enough for an agent to use correctly.

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

Parameters5/5

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

Even with 100% schema coverage, the description adds meaningful semantics: it explains how `since` and `timeout` interact, clarifies the default behaviors, and gives the `next_since` pattern that ties parameters to a stateful usage loop. This goes beyond schema definitions.

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?

The description opens with 'Long-poll for a new DM', a specific verb and resource that clearly differentiates from siblings. It explicitly contrasts with read_inbox ('same shape, but no busy-polling'), making the tool's unique purpose unambiguous.

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?

It explicitly says 'Use this as your idle loop instead of read_inbox', naming the alternative and when to choose this tool. It also provides a standard pattern ('pass `next_since` from the previous call as `since`'), which is practical guidance.

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

All Apuchat toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources