Skip to main content
Glama

Hail Communication for AI

Get events

get_events
Read-onlyIdempotent

Read a page of workspace events or events for one resource.

    A call-specific response includes the current ``call_status``.
    Terminal call states are completed, failed, busy, no_answer and canceled.
    The response is a snapshot, not a streaming subscription.
    Returns ``items``, ``next_cursor`` and optional ``call_status``, or an error.

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

Input Schema

NameRequiredDescriptionDefault
idNoOne resource: ``call:<uuid>``, ``email:<uuid>`` or ``sms:<uuid>``, with the ID from ``place_call``, ``send_email``, ``send_sms`` or their list tools. Omitted: events for the whole workspace.
kindNoOnly events of this type, such as state_change, agent_turn, user_turn, tool_call or error.
limitNoHow many items one page holds. ``next_cursor`` in the response points to the next page.
cursorNoPagination cursor: the ``next_cursor`` from the previous page. Omitted: the first page.
llm_modelNoModel ID of the calling agent. Optional. Recorded for analytics only.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / limit / description
      Previous value: -"Number of items per page."New value: +"How many items one page holds. ``next_cursor`` in the response points to the next page."
    • addedInput schema / properties / llm_model
      Added value: +{
      +  "description": "Model ID of the calling agent. Optional. Recorded for analytics only.",
      +  "type": "string"
      +}
  2. Changed3 schema fields changed
    • changedInput schema / properties / limit / description
      Previous value: -"Page size, 1 to 1000."New value: +"Number of items per page."
    • addedInput schema / properties / limit / maximum
      Added value: +1000
    • addedInput schema / properties / limit / minimum
      Added value: +1
  3. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive), so the description's job is to add context, which it does: it discloses that the response is a snapshot rather than a streaming subscription and enumerates terminal call states (completed, failed, busy, no_answer, canceled). It does not mention rate limits or pagination cost, but the snapshot caveat is genuinely useful framing an agent would otherwise have to guess.

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?

Front-loaded lead sentence followed by short behavioral lines; each earns its place except the trailing "Returns items, next_cursor and optional call_status," which duplicates the output schema. No filler or marketing language.

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?

Complete for a five-parameter, all-optional read tool with a rich output schema and full annotation coverage. The only gap is guidance relative to sibling event tools, which the description never addresses.

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?

Schema description coverage is 100%, including the id format, cursor semantics and limit bounds, so the schema carries the burden. The description adds only the workspace-vs-resource framing, which is already in the id parameter's own description. Baseline 3.

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 first sentence gives a specific verb and resource ("Read a page of workspace events or events for one resource") and distinguishes workspace-wide from single-resource scope. It stops short of differentiating itself from the sibling get_email_events, which reads as an overlapping event-listing tool.

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?

Usage is only implied: pass an id for one resource, omit it for the whole workspace. There is no explicit when-to-use or when-not-to-use guidance, and the presence of get_email_events in the sibling set makes the omission consequential.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources