Skip to main content
Glama
businessapi-mcp

businessapi-mcp

by JoeFu

List Monitoring Events

list_monitoring_events
Read-only

List detected ASIC/ATO/ABRS/PPSR changes for monitored entities, filter by entity, and resume from a prior event ID or date to catch up after webhook downtime.

Instructions

List detected changes (summary form: monitoringEventId, entityId, eventType, title, detectedAt, simulated).

Without entity_id: ALL your events, oldest first (GET /monitoring/events). since = the last monitoringEventId you processed (returns later events) or an ISO 8601 date-time — store the last id to catch up after webhook downtime. With entity_id: that entity's events, newest first. per_page max 100. eventType: document_lodged, name_change, address_change, status_change, type_change, gst_change, business_name_added, business_name_removed, insolvency_notice, ppsr_registration, trade_mark_filed / _status_change / _owner_change / _renewal_due / _renewed, register_added / _status_change / _removed / _conditions_change, other_change (treat unknown as other_change). Use get_monitoring_event for description, source, effectiveDate and metadata (oldValue/newValue, documentType …).

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

Input Schema

NameRequiredDescriptionDefault
pageNo
sinceNo
per_pageNo
entity_idNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.7/5.0
Behavior5/5

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

Annotations only supply readOnlyHint and openWorldHint; the description adds non-obvious behavior the annotations cannot express: result ordering flips (oldest first without entity_id, newest first with it), per_page is capped at 100, and the summary payload omits fields that require a second call. It also tells the agent to normalize unrecognized event types to other_change rather than fail.

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 the scope decision and return shape before the detail; every sentence is actionable. The eventType enumeration is long, but since the schema declares zero enums it is the only source of allowed values and therefore earns its space, though it could be formatted more compactly.

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?

For a four-parameter read tool with an output schema and safety annotations already covered, this is close to complete: ordering, page-size cap, cursor semantics, fallback for unknown types, and the escalation path are all present. Only pagination via the undocumented page parameter and any rate-limit behavior are left out.

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 0%, so the description must carry meaning, and it does for three of four parameters: since accepts either a monitoringEventId cursor or an ISO 8601 date-time, per_page maxes at 100, and entity_id switches both filtering and sort order. The page parameter is never mentioned, leaving one parameter to be inferred from the schema defaults alone.

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?

Opens with a specific verb+resource ("List detected changes") and immediately scopes the result shape (summary form with named fields), then distinguishes the two modes by whether entity_id is present. It is unambiguously separable from get_monitoring_event, which it explicitly delegates detail to.

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?

Explicit routing: the no-entity mode returns all your events; the entity mode returns that entity's events; and the description names the sibling get_monitoring_event for description/source/effectiveDate/metadata. It also gives a concrete operational pattern (store the last monitoringEventId to catch up after webhook downtime), which is exactly the when-to-use guidance an agent needs.

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