Skip to main content
Glama
businessapi-mcp

businessapi-mcp

by JoeFu

Call Endpoint

call_endpoint
Destructive

Calls any Business API v2 endpoint without a dedicated tool, enabling ASIC forms, entity monitoring, webhooks, and staged ABN data access via relative paths.

Instructions

Call any Business API v2 endpoint that has no dedicated tool (ASIC forms, entity monitoring, webhooks, staged ABN data…).

path is RELATIVE to the v2 root, e.g. "/asic-484-forms", "/monitoring/entities/123", "/helpers/entitlement-questionnaire". Never include /api/v2 or /api/test/v2 — the server adds the right prefix for its environment. Find paths in resource bapi://docs/endpoints; field schemas are on https://businessapi.com.au/developers/api/. POST = lodge (returns requestId; follow with get_request_status). Live writes are blocked unless BAPI_ALLOW_LIVE=true. Prefer the typed lodge_* tools for company / ABN / business-name registrations: they validate before sending.

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": {
      "method": "<method>",
      "path": "<path>"
    },
    "name": "call_endpoint"
  }
}

Input Schema

NameRequiredDescriptionDefault
bodyNo
pathYes
queryNo
methodYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.9/5.0
Behavior5/5

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

Beyond the destructiveHint/openWorldHint annotations, the description discloses the environment gate ('Live writes are blocked unless BAPI_ALLOW_LIVE=true'), the POST-lodge side effect and its requestId return, and the server-side prefix rewriting. These are exactly the non-obvious behaviors an agent needs before invoking a destructive open-world tool.

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?

Front-loaded with the core capability, then the highest-risk detail (path format) before secondary notes. Every sentence carries distinct operational information — examples, prefix rule, doc pointers, POST follow-up, environment gate, sibling preference — with no repetition of the schema or annotations.

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?

An output schema exists, so return values need not be explained, yet the description still notes the requestId from POST and the polling path. For an escape-hatch tool with an unbounded endpoint surface, it covers invocation, discovery, safety gating, and follow-up completely.

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 carries the burden: it fully specifies path semantics (relative to v2 root, never include /api/v2, with three literal examples) and gives method semantics (POST = lodge). Body and query are left to external documentation pointers rather than described inline, which is a real but reasonable gap given the open-ended endpoint surface.

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?

The description gives a specific verb and resource ('Call any Business API v2 endpoint') and immediately bounds the scope to endpoints 'that has no dedicated tool'. It names concrete examples (ASIC forms, entity monitoring, webhooks, staged ABN data), so an agent can tell this apart from the typed lodge_* and get_* siblings 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 Guidelines5/5

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

Explicit when-to-use (endpoints lacking a dedicated tool), explicit when-not (prefer lodge_* tools for company/ABN/business-name registrations because they validate first), and an explicit follow-up step for POST (poll get_request_status). It also routes the agent to the resource bapi://docs/endpoints for path discovery, leaving nothing to inference.

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