Skip to main content
Glama
businessapi-mcp

businessapi-mcp

by JoeFu

Search Business Industries

search_business_industries
Read-only

Search the ATO main business activity list by keyword to find industry codes and names for ABN applications. Returns ranked matches with 4-digit codes and ANZSIC classes.

Instructions

Search the ATO main-business-activity list by keyword (e.g. "cleaning", "software", "cafe"). Free helper.

Returns {searchTerm, activitiesCount, activities: [{score, code, industryCode, fullName}]} ranked by relevance. Use code (4 digits, e.g. 7749) as businessActivity.code and fullName as businessActivity.description in an ABN application; industryCode is the ANZSIC class. The endpoint needs a search term — there is no full list.

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": {
      "search_term": "<search_term>"
    },
    "name": "search_business_industries"
  }
}

Input Schema

NameRequiredDescriptionDefault
search_termYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, so the safety profile is covered; the description adds that it is a free helper, that results are relevance-ranked, and that a search term is mandatory with no enumeration endpoint. The semantic distinction between `code` and `industryCode` is exactly the kind of context annotations cannot 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?

Purpose is front-loaded and the field-mapping guidance earns its space. The standalone fragment "Free helper." and slight line-break choppiness cost a bit of polish, but no sentence is padding.

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 one-parameter lookup with an output schema and read-only annotations, the definition covers the essentials: what it searches, what comes back semantically, and how to use the fields downstream. It could note result caps or how broad terms behave, but nothing critical for correct invocation 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 coverage is 0% for the single `search_term` parameter, but the description compensates with example keywords ("cleaning", "software", "cafe") and an explicit statement that the endpoint requires a term. That gives enough to construct valid input without guessing.

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 — searching the ATO main-business-activity list by keyword — with concrete example terms. It is clearly a lookup helper, distinguishable from the lodge_* and get_* siblings that submit or fetch applications.

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?

Explains the downstream use case precisely: feed `code` into businessActivity.code and `fullName` into businessActivity.description for an ABN application, which tells an agent when this tool belongs in a workflow. It also warns there is no full-list mode. It stops short of naming an explicit alternative or exclusion, so not a 5.

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