Skip to main content
Glama

Asx Announcements

Asx Get Company

asx_get_company
Read-onlyIdempotent

Company details for an ASX-listed company by ticker: name, description, listing date, sector, head office, directors and secretaries, website, shares on issue, market capitalisation, last/bid/ask price, 52-week range, ISIN, latest dividend and headline financials. Source: ASX company information (delayed).

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "ticker": "LTR"
    },
    "name": "asx_get_company"
  }
}

Input Schema

NameRequiredDescriptionDefault
tickerYesASX code, e.g. "BHP", "LTR", "PLS"

Output Schema

NameRequiredDescriptionDefault
isinNo
nameNo
priceNo
listedNo
sectorNo
sourceNo
tickerNo
websiteNo
currencyNo
dividendNo
directorsNo
data_as_ofNo
financialsNo
market_capNo
descriptionNo
head_officeNo
secretariesNo
share_classNo
industry_groupNo
share_registryNo
shares_on_issueNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, openWorld, and non-destructive, so safety needs no restating. The description adds one genuinely useful behavioral fact beyond them: the data is delayed ASX information. It says nothing about behavior for invalid or delisted tickers, which would have raised this score.

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?

One sentence, front-loaded with the action and keying parameter, followed by the field inventory. The long enumeration is dense but each item tells the agent what it will receive; the source note is tacked on but brief.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With an output schema present, the field list is largely redundant, and the description omits anything about invalid-ticker behavior or coverage limits. For a simple one-parameter lookup with full schema and annotation coverage this is adequate, but not more.

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 coverage is 100% and the single parameter already carries examples ('BHP', 'LTR', 'PLS'). The description only reinforces that the ticker is an ASX code for a listed company, adding no syntax or format detail beyond the schema, 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?

The description gives a specific verb+resource ('Company details for an ASX-listed company by ticker') and enumerates the payload (listing date, sector, directors, ISIN, dividends, etc.), so an agent knows exactly what this returns. It does not name siblings like asx_get_announcements or asx_get_share_issues, but the field enumeration makes the resource distinction obvious 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 Guidelines2/5

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

There is no explicit when-to-use, when-not-to-use, or alternative guidance. The only contextual cue is 'by ticker' and the data source note, leaving the agent to infer that this is the profile lookup versus the announcements/share-issues siblings.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.