Skip to main content
Glama

run_au_companies_search

Search Australia's company registry (ASIC/ABN) by name to retrieve registration numbers, status, addresses, and links. Use it to verify or research Australian businesses.

Instructions

Search the Australia company registry (ASIC / ABN) by company name: name, registration number, status, address and link. 1 point per returned record.

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": {
      "keyword": "<keyword>"
    },
    "name": "run_au_companies_search"
  }
}

Input Schema

NameRequiredDescriptionDefault
statusNoStatus. Options: active = Active, inactive = Inactive / dissolved
keywordYesCompany name. e.g. woolworths
max_itemsNoMax items (up to 250)
start_pageNoStarting page

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.0.1

TDQS

A3.5/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full burden. It usefully discloses the billing model ('1 point per returned record'), which is real behavioral value, but says nothing about auth, rate limits, or what happens with zero matches.

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?

A single tight sentence that front-loads the action and scope. Efficient, though the trailing field list and cost note make it slightly dense rather than optimally structured.

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?

With no output schema, the description usefully enumerates the return fields (name, registration number, status, address, link), which compensates for the missing output schema. Pagination semantics are left to the schema, but overall it is complete enough to invoke correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so the schema already documents keyword, status, max_items and start_page. The description adds no syntax or format detail beyond what the schema provides, so the baseline 3 applies.

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?

States a specific verb (Search) and resource (Australia company registry / ASIC / ABN), plus the fields returned. 'By company name' hints at how it differs from the run_au_companies sibling, but it never explicitly contrasts with it, so an agent must infer the 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?

Usage is only implied: the phrase 'by company name' suggests you supply a name to search. There is no explicit when-to-use statement, no exclusions, and no reference to the many sibling company-registry tools (run_au_companies, run_nz_companies_search, etc.).

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

Deploy Server

Other Tools