Skip to main content
Glama
businessapi-mcp

businessapi-mcp

by JoeFu

Start Entity Monitoring

start_entity_monitoring
Idempotent

Monitor companies (ACN) and ABN holders for public-register changes across ASIC, ABR, PPSR and related sources, prepaid for 12 months, with change webhooks and event listings.

Instructions

Start monitoring up to 25 companies (acn) and/or ABN holders (abn) for public-register changes, prepaid 12 months each.

LIVE cost $18.00 per entity (card billing required); sandbox $0. Sources: ASIC, ABR, insolvency notices and PPSR (companies), IP Australia trade marks, ASIC licence registers, ACNC. Changes arrive as monitoring.change_detected webhooks and through list_monitoring_events. Read bapi://docs/entity-monitoring first. entities: [{acn}, {abn}, {acn, abn}], each with an optional reference (≤100 chars) of your own. ARBNs are not accepted. idempotency_key: YOUR unique string for this order (≤255 chars, e.g. "order-2026-11-18-acme"). A retried call with the same key never charges twice — reuse it when retrying after a timeout or a 202 "processing" answer. Response 201 {unitPrice, total (cents), entities: [entity objects]}; 422 validation_failed carries per-row errors (already_monitored -> renew_entity_monitoring; stopped_with_time_remaining -> resume_entity_monitoring); nothing charged on errors. dry_run=true (default) validates locally and returns the payload.

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": {
      "entities": "<entities>",
      "idempotency_key": "<idempotency_key>"
    },
    "name": "start_entity_monitoring"
  }
}

Input Schema

NameRequiredDescriptionDefault
dry_runNo
entitiesYes
idempotency_keyYes

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?

Goes well beyond the annotations: discloses real dollar cost ($18.00/entity live, $0 sandbox), that card billing is required, that entities are prepaid 12 months, that nothing is charged on errors, and that an idempotency_key retry never charges twice. It also discloses delivery mechanics (monitoring.change_detected webhooks and list_monitoring_events) and the 201/422 response shapes, which the annotations alone could not convey.

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-loads purpose, cap, and price before mechanics, and every block — cost, sources, entities, idempotency, response, dry_run — carries information an agent needs. The dense multi-clause line breaks make it slightly harder to scan than a cleanly sectioned description, but there is no filler to cut.

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?

Complete for a paid, mutating, idempotent operation: cost model, billing prerequisite, validation-first default, failure semantics with per-row errors and sibling routing, and delivery channel are all covered. An output schema exists, and the description still summarizes the 201 body only briefly, which is proportionate.

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

Parameters5/5

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

With schema description coverage at 0% (top level), the description carries the full burden and does: it documents the entity tuple shapes ({acn}, {abn}, {acn, abn}), the optional `reference` capped at 100 chars, the ACN/ABN format constraints and ARBN exclusion, and the idempotency_key contract (≤255 chars, example value, retry semantics). All three parameters and the nested row structure gain meaning not present in the schema.

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 ("Start monitoring up to 25 companies (acn) and/or ABN holders (abn)") plus the scope (public-register changes, prepaid 12 months each) and the data sources. It also names the sibling tools it is not — renew_entity_monitoring and resume_entity_monitoring — so the agent can distinguish start-new from renew/resume without opening a schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives a clear operating context: read bapi://docs/entity-monitoring first, ARBNs are not accepted, and dry_run=true is the default so the agent knows the first call is a local validation. Alternative routing is present but framed reactively in the 422 error mapping (already_monitored -> renew_entity_monitoring; stopped_with_time_remaining -> resume_entity_monitoring) rather than as upfront when-to-use guidance, which keeps it short of a 5.

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