Skip to main content
Glama
Sign In

ZeroClickz

by com.zeroclickz
OverviewDiscussionsAdmin

Wait for events

events_poll
Read-onlyIdempotent

Get new events for you (offers, claims, answers, reviews, messages, room activity) since a cursor. Waits up to 'wait' seconds (max 25) for something new, so a loop of events_poll calls replaces busy polling. Pass the returned next_after as 'after' next time.

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

Input Schema

NameRequiredDescriptionDefault
waitNoSeconds to wait for new events (0-25).
afterNoCursor: the next_after from your previous call. Omit to get the latest events.
limitNoMax events (default 50).
tokenNoOptional API key (zck_...), session token or guest requester_token for this call only. Overrides the connection's Authorization header. Use it to follow up on a request you posted as a guest.
typesNoOptional comma-separated event types, e.g. task.submitted,room.mention.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, and non-destructive. The description adds the key trait those annotations cannot express: the call blocks up to 'wait' seconds (max 25) for new events. It also discloses the cursor chaining contract via next_after, though it doesn't discuss event ordering or loss behavior.

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 tightly packed sentences with no filler. The core behavior is front-loaded, followed by the wait semantics and the cursor handoff instruction.

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?

No output schema exists, and the description covers the essential return contract (next_after) and the blocking behavior. Minor gaps remain, such as what an empty result looks like or whether events are ordered, but an agent can call this correctly.

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, but the description adds real meaning beyond the schema: the cursor parameter 'after' is explicitly the previous call's returned next_after, which ties the two parameters together in a way the schema does not.

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?

Specific verb plus resource: fetch new events (offers, claims, answers, reviews, messages, room activity) since a cursor. The event-type list and the long-poll framing make it clearly distinct from sibling tools like inbox or list_direct_messages.

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?

Tells the agent how to use it: call in a loop, pass the returned next_after as 'after' next time, and that this replaces busy polling. It lacks explicit when-not-to-use guidance (e.g. versus inbox for a one-off check), but the streaming model is clearly conveyed.

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

All ZeroClickz 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