Skip to main content
Glama
businessapi-mcp

businessapi-mcp

by JoeFu

Get Abn Entitlement Questionnaire

get_abn_entitlement_questionnaire
Read-only

Retrieves the ABN entitlement questionnaire for a given ATO entity type and subtype, guiding applicants through required questions and recording answers for ABN registration lodgement.

Instructions

Fetch the ABN entitlement questionnaire for an ATO entity type / sub-type (e.g. 117/006 sole trader, 051/027 private company, 161/150 partnership, 212/077 trading trust, 210/196 SMSF; codes in bapi://docs/ato-codes). Free helper.

Walk the applicant through the questions and record each step as {questionId, answerId, nextQuestionId} in entitlement.questionnaire, plus firstQuestion / outcomeId / outcome, for lodge_abn_registration.

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": {
      "entity_type": "<entity_type>",
      "entity_sub_type": "<entity_sub_type>"
    },
    "name": "get_abn_entitlement_questionnaire"
  }
}

Input Schema

NameRequiredDescriptionDefault
entity_typeYes
entity_sub_typeYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.4/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 does not need to re-establish safety; instead it adds real context: the call is free, it is a multi-step walkthrough that requires recording {questionId, answerId, nextQuestionId} plus firstQuestion/outcomeId/outcome, and it points to bapi://docs/ato-codes for code lookups. It stops short of saying whether the questionnaire state must be persisted between calls or how large the question set is.

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?

Two sentences, front-loaded with the purpose before the workflow detail, and the code examples are dense but functional rather than filler. The parenthetical example list is long relative to the sentence, though each pair demonstrates a genuinely distinct entity category.

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 no prose, and the description does the remaining work: it identifies the input domain, the output destination (`entitlement.questionnaire`), and the downstream consumer tool. For a two-parameter lookup with rich annotations, nothing an agent needs in order to call it correctly is missing.

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 full burden, and it does compensate well by giving four worked entity_type/entity_sub_type pairs and directing the agent to bapi://docs/ato-codes for the full code list. It still does not say what happens with an unrecognised pair or whether sub-type can be omitted, so a small ambiguity remains.

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 opens with a specific verb and resource ('Fetch the ABN entitlement questionnaire') and scopes it to an ATO entity type/sub-type, then lists concrete code pairs (117/006 sole trader, 051/027 private company, etc.). It also distinguishes itself from the sibling it feeds ('for lodge_abn_registration'), so an agent can separate this from the lodging tool without opening the 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?

It states the context clearly: this is the preparatory step whose output populates `entitlement.questionnaire` for `lodge_abn_registration`, and it labels itself a 'Free helper', signalling it is the cheap call to make before lodging. It does not state explicit when-not-to-use conditions or name alternative questionnaire sources, so it falls short of a full 5.

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