Skip to main content
Glama
businessapi-mcp

businessapi-mcp

by JoeFu

List Monitored Entities

list_monitored_entities
Read-only

Retrieve monitored entities with filters for status, ACN, ABN, or expiration date to support renewal runs and compliance reviews.

Instructions

List monitored entities (data[] of entity objects + meta {currentPage, perPage, total, lastPage}). Filters: status, acn, abn, expires_before (YYYY-MM-DD, for renewal runs). per_page max 100. Entity object: id, acn, abn, entityName, reference, status, monitoringStatus (pending|active|degraded|inactive), startsAt, expiresAt, daysRemaining, lastEventAt, entityStatus (registered|deregistered|cancelled|external_administration| strike_off_proposed|unknown), entityType, gstRegistered, gstDate, businessNames[].

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_monitored_entities"
  }
}

Input Schema

NameRequiredDescriptionDefault
abnNo
acnNo
pageNo
statusNo
per_pageNo
expires_beforeNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/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; the description adds the per_page ceiling of 100 and the pagination meta shape, which are real behavioral constraints. It says nothing about rate limits, auth/scoping (e.g. whether results are limited to the caller's account), or result ordering, so it adds only modest context beyond 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-loads purpose and response envelope, then itemizes filters and fields compactly with no filler sentences. Some space is spent enumerating entity fields that the output schema already defines, which is slightly redundant but not wasteful.

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 six-parameter read-only list tool with an output schema and safety annotations, the definition covers filters, pagination limits, and result shape well enough to call correctly. The remaining gaps — status enum meaning and default ordering — are narrow but real.

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 the load, and it does for most parameters: it identifies status, acn, abn, expires_before (with the YYYY-MM-DD format and renewal-run intent) and the per_page max. It leaves `page` unexplained and never reconciles the input status enum (processing|active|stopped|expired) with the different monitoringStatus/entityStatus values it enumerates, which is the main ambiguity an agent would hit.

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?

Opens with a specific verb+resource ("List monitored entities") and immediately shows the response envelope (data[] + meta pagination), so the agent knows exactly what operation this is. It does not name the singular sibling get_monitored_entity or explain how the two differ, so it stops short of full distinction.

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?

Gives a targeted usage cue for one filter — expires_before "for renewal runs" — which is genuinely helpful context for when to reach for it. However, there is no guidance on when to use this list versus get_monitored_entity or list_monitoring_events, and no stated prerequisites or exclusions.

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