Skip to main content
Glama
businessapi-mcp

businessapi-mcp

by JoeFu

Get Account Status

get_account_status
Read-only

Retrieve account and plan status plus usage counters for the current API key to diagnose 403 errors and plan limits.

Instructions

Account / plan state for the current API key: accountName, companyName, abn, createdAt, planId, planCreatedAt, planEndsAt and stats {abnLodgementForms, taxLodgementForms, acnLodgementsForms, acnRegisteredAgentForms, bnLodgementsForms, bnRenewLodgementsForms, bapiHelpers} (usage counters). Use it to explain 403s and plan limits.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the description only needs to add value, and it does: it discloses that the result is keyed to the caller's own credential (an auth-context fact) and that the stats block is usage counters rather than business data. It doesn't cover rate limits or whether other keys see different data, which keeps it below a 5.

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?

The purpose and the 403/plan-limit guidance are front-loaded and useful, but the long inline enumeration of return fields and the nested stats object largely restates what the output schema already provides. That bulk pushes the actionable guidance to the end of a dense sentence.

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 zero-parameter, read-only diagnostic endpoint with a declared output schema, the description supplies enough: what it returns, whose account it reflects, and why an agent would call it. Only minor gaps remain, such as whether it is safe to call defensively before other operations.

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?

The tool takes no parameters, so there is nothing for the description to disambiguate; the baseline of 4 applies. The description correctly reflects the zero-argument nature by scoping everything to 'the current API key'.

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 resource and scope: account/plan state for the current API key, and enumerates the fields returned. The scope phrase ('current API key') clearly separates it from the many sibling tools that report status of a specific lodged request or form, which all take an identifier.

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?

'Use it to explain 403s and plan limits' gives a concrete trigger for invoking the tool, which is the main ambiguous case an agent faces with a zero-parameter account endpoint. It stops short of naming an alternative or stating when not to call it, but the trigger context is clear.

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