Skip to main content
Glama

poll_events

Retrieve recent events from a timestamp for real-time visibility into CI results, deployments, and file changes when push notifications are unavailable.

Instructions

Get new events since a timestamp (push notification fallback)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
sinceNoISO 8601 timestamp — returns events after this time

Implementation Reference

  • Handler implementation for the 'poll_events' tool, which fetches events either from a specific timestamp or the 100 most recent ones.
    private async handlePollEvents(args: Record<string, unknown>) {
      const schema = z.object({ since: z.string().optional() });
      const parsed = schema.parse(args);
    
      const events = parsed.since
        ? getEventsSince(parsed.since)
        : getRecentEvents(100);
    
      return {
        content: [{
          type: 'text' as const,
          text: JSON.stringify(events, null, 2),
        }],
      };
    }
  • src/server.ts:159-167 (registration)
    Registration of the 'poll_events' tool in the ListToolsRequestSchema handler.
      name: 'poll_events',
      description: 'Get new events since a timestamp (push notification fallback)',
      inputSchema: {
        type: 'object',
        properties: {
          since: { type: 'string', description: 'ISO 8601 timestamp — returns events after this time' },
        },
      },
    },
Behavior3/5

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

With no annotations provided, the description carries the full disclosure burden. It successfully adds the 'push notification fallback' behavioral context but fails to clarify critical operational details: whether polling consumes/removes events from a queue, handling of duplicate events, or pagination limits for large event sets.

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?

The description is a single, highly efficient sentence that front-loads the action ('Get new events') and places contextual clarifiers at the end. Zero wasted words; every token earns its place in guiding tool selection.

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

Completeness3/5

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

Given the tool's simplicity (one optional parameter, no nested objects) and clear naming convention relative to sibling watch tools, the description provides adequate context for selection. However, the absence of an output schema and lack of description regarding return event structure or consumption behavior leaves minor gaps in operational context.

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?

Input schema coverage is 100% with the 'since' parameter fully documented as an 'ISO 8601 timestamp'. The description mentions 'since a timestamp' but adds no additional semantic value (e.g., 'use the timestamp returned by the previous poll') beyond the schema definitions, meeting the baseline for high-coverage schemas.

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?

The description uses a specific verb ('Get') and resource ('events') with clear scope ('since a timestamp'). The parenthetical '(push notification fallback)' effectively distinguishes this from the sibling watch_* tools by clarifying its architectural role as a polling alternative to push notifications.

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

Usage Guidelines3/5

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

The phrase 'push notification fallback' implies when to use this tool (when push mechanisms are unavailable), positioning it against the watch_* siblings. However, it lacks explicit guidance on when-not-to-use or prerequisites, requiring the agent to infer the usage pattern from the 'fallback' hint alone.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/jarvisassistantux/loopsense'

If you have feedback or need assistance with the MCP directory API, please join our Discord server