Skip to main content
Glama
murtazox04

Cue

by murtazox04
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

get_event

Read-only

Fetch a reported event by ID from Cue to inspect its processing status, matched rules, and generated messages. Use it after sending to see what was sent and why.

Instructions

Fetch a reported event by id and, for each rule listening for its name, whether the rule fired and what came of it. Use it after send_event to learn what was sent and why or why not; follow a message_id with get_message for delivery, and use explain for a dry run instead. Needs the messages:read scope.

Returns id, name, source, idempotency_key, data, status (pending until the worker runs the rules, then processed, or failed with the reason in error), occurred_at, received_at and outcome: null while pending, else one entry per rule with rule, matched, reason, status, message_id and digest_id. matched: false comes with condition_false, outside_rollout or condition_error. A composed message has status and message_id, and reason is its status_reason when suppressed (e.g. agent_budget: …, unsubscribed); digested means it joined digest_id; agent_not_allowed means the agent may not use the rule's category. An empty list means no rule listens for the name. Fails with 404 when the id does not exist or, for an agent key, was reported by another sender.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
event_idYesEvent UUID: the `id` returned by send_event, or a message's `event_id` from get_message.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.1.1
    • addedInput schema / properties / event_id / description
      Added value: +"Event UUID: the `id` returned by send_event, or a message's `event_id` from get_message."
  2. First observedv0.1.0

TDQS

A4.6/5.0
Behavior5/5

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

Annotations only cover the read-only/open-world profile, but the description adds the required `messages:read` scope, the 404 failure conditions (nonexistent id or agent key from another sender), and the pending/processed/failed lifecycle of `status`. That is substantial behavioral context beyond the annotations.

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 with purpose and usage before the return-shape detail, and every clause carries information. It is dense and long, but with no output schema the field documentation earns its space, so only minor trimming is possible.

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?

With no output schema, the description fully documents the returned fields and enumerates the matched/reason/status semantics, including suppressed-message cases and the empty-list meaning. Nothing an agent needs to interpret the result is missing.

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 coverage is 100% and the description largely restates the schema's own guidance (send_event id or a message's event_id). It adds no format or syntax detail beyond it, so the baseline 3 is appropriate.

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 ('Fetch a reported event by id') plus the exact scope of the response (per-rule fired/outcome detail). This distinguishes it clearly from get_message, send_event, and explain without needing to open the 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?

Explicitly says 'Use it after send_event to learn what was sent and why or why not', routes delivery questions to get_message, and names explain for dry runs. When-to-use and alternatives are both fully specified.

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