Skip to main content
Glama

PeppolStatus

by com.peppolstatus
OverviewDiscussionsAdmin

list_events

Read-only

List global change events

Every typed change event, newest-first, cursor-paginated. Any anomaly an event triggered is embedded on it. cursor walks older events; prev_cursor walks the newer edge (for live polling). The first page carries a meta block with exact type facets + filter count and an auto-bucketed timeline chart.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
hostNoFilter to events for one host.
seatNoFilter to events referencing one seat.
typeNoComma-array of change-event types (a single value is valid).
limitNoPage size, clamped to [1, 200]. Defaults to 50.
sinceNoOnly include items at or after this ISO 8601 instant.
untilNoOnly include events at or before this ISO 8601 instant.
cursorNoOpaque pagination cursor returned as `next_cursor` by the previous page.
doctypeNoFilter to events touching one document-type URN. Matches both payload shapes: the merged `endpoint_changed` `doctypes` array and the legacy singular `doctype` on pre-merge rows.
participantNoFilter to one participant (`scheme::value`).
prev_cursorNoOpaque newer-direction cursor (from a page's `prev_cursor`): returns events newer than it, newest-first. Mutually exclusive with `cursor`.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / type / items / enum
      Previous value: -[
-  "participant_registered",
-  "participant_deregistered",
-  "participant_smp_changed",
-  "endpoint_changed",
-  "doctype_support_changed",
-  "ap_seat_changed",
-  "host_cert_rotated",
-  "hosting_changed",
-  "directory_card_changed"
-]New value: +[
+  "participant_registered",
+  "participant_deregistered",
+  "participant_smp_changed",
+  "endpoint_changed",
+  "doctype_support_changed",
+  "ap_seat_changed",
+  "host_cert_rotated",
+  "hosting_changed",
+  "directory_card_changed",
+  "software_changed",
+  "version_changed"
+]
  2. Changed1 schema field changed
    • addedInput schema / properties / doctype
      Added value: +{
+  "description": "Filter to events touching one document-type URN. Matches both payload shapes: the merged `endpoint_changed` `doctypes` array and the legacy singular `doctype` on pre-merge rows.",
+  "type": "string"
+}
  3. First observed

TDQS

A4.1/5.0
Behavior5/5

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

Given `readOnlyHint: true` already declares the safety profile, the description adds meaningful behavioral detail: cursor direction semantics, embedded triggered anomalies, and the meta block with facets and timeline chart. The description is consistent with the read-only annotation and enriches it with concrete pagination and payload 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?

The description is four dense sentences with no filler. The core purpose is front-loaded, followed by pagination semantics, embedded anomalies, and meta information — each sentence adds necessary information.

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?

The description is surprisingly complete for a 10-parameter list tool without an output schema: it covers ordering, pagination, anomaly embedding, and page metadata. It does not enumerate the exact event payload fields, but the 'typed change event' framing plus the schema's type enum lowers the cost of that omission. Still, an output schema or a more explicit event-shape summary would raise completeness further.

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 description coverage is 100%, so each parameter is already documented and the baseline is 3. The description adds value beyond the schema by explaining the different directions of `cursor` vs `prev_cursor`, the 'live polling' use case, and the meta block generated for the first page.

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 states a specific verb and resource, 'List global change events,' and key ordering behavior, 'newest-first.' It is clear and distinct from incident/anomaly-related siblings, although it doesn't explicitly name an alternative sibling for comparison.

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 description conveys usage context through pagination direction: `cursor` walks older events, `prev_cursor` walks newer events and is 'for live polling.' However, it provides no explicit when-to-use vs when-not-to-use guidance or alternative tool names, so comparative selection is left to the agent's inference.

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

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