Skip to main content
Glama
businessapi-mcp

businessapi-mcp

by JoeFu

Get Monitoring Event

get_monitoring_event
Read-only

Retrieves full details of a monitoring event by ID, including source, effective date, metadata changes, and the affected entity for registry monitoring.

Instructions

One monitoring event in full: description, source (asic|abr|insolvency|ppsr|trademark|register), effectiveDate, metadata (field/oldValue/newValue; documentType/documentNumber for document_lodged; businessName; previousName; noticeUrl; tradeMark*; registerLabel/registerStatus/licenseeNumber/registerUrl; gstCancelled) and the entity object.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "event_id": "<event_id>"
    },
    "name": "get_monitoring_event"
  }
}

Input Schema

NameRequiredDescriptionDefault
event_idYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered and the bar is lower. The description adds no behavioral context beyond that — nothing about what happens when an event_id does not exist, whether the event can be stale or pending, or any auth/rate considerations for an open-world lookup.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

It is a single front-loaded sentence with no filler prose, but most of its length is a parenthetical field dump that largely duplicates the output schema rather than earning its place.

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

Completeness2/5

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

An output schema exists, so the long enumeration of return fields is redundant, while the genuinely missing pieces — the meaning of event_id and when to prefer this over list_monitoring_events — are absent. For a simple read tool that is not fatal, but the description is complete in the wrong dimension.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

There is one parameter with 0% schema description coverage, and the description never mentions event_id or its expected form. Instead it spends its words on output fields (source enum values, effectiveDate, metadata sub-keys), leaving the only input entirely undocumented.

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 phrase "One monitoring event in full" states a specific resource and cardinality, which implicitly distinguishes it from list_monitoring_events. However, the sentence is dominated by an enumeration of returned fields rather than a statement of the operation, so the verb (fetch by id) must be inferred from the tool name.

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: the required event_id suggests retrieval of a known event, and "in full" hints that this is the detailed counterpart to a list call. There is no explicit when-to-use, no when-not-to-use, and no named alternative such as list_monitoring_events.

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