Skip to main content
Glama

Asx Announcements

Asx Get Announcements

asx_get_announcements
Read-onlyIdempotent

List ASX company announcements for a listed Australian company by ticker: date and time (Sydney), headline, price-sensitive flag, page count, file size, a derived category (share_issue, unquoted_securities, cessation_of_securities, buyback, director_interest, substantial_holder, trading_halt, quarterly_cashflow, results, meeting, other) and a document link. Newest first. Source: ASX company announcements. Use asx_get_share_issues for dilution questions.

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": {
      "limit": 10,
      "months": 6,
      "ticker": "LTR"
    },
    "name": "asx_get_announcements"
  }
}

Input Schema

NameRequiredDescriptionDefault
yearNoFull calendar year instead of a rolling window, e.g. 2025
limitNoMax rows to return (default 50, max 300)
monthsNoLook-back window in months (default 6). Ignored when year is given.
tickerYesASX code, e.g. "BHP", "LTR", "PLS"
categoryNoOnly this derived category
price_sensitive_onlyNoOnly market-sensitive announcements

Output Schema

NameRequiredDescriptionDefault
sourceNo
tickerNo
windowNo
matchedNo
returnedNo
data_as_ofNo
announcementsNo
total_in_windowNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/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 the safety profile is covered. The description adds genuine behavioral context: results are ordered newest-first, the source is ASX company announcements, and the category values are derived rather than raw ASX labels. It does not address pagination or truncation behavior at the 300-row cap.

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?

The first sentence front-loads verb, resource and scope, followed by two short routing/attribution sentences. The long field enumeration is dense but each item is a distinct returned value; there is no filler or hedging.

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 an output schema present, return values need not be explained, yet the description still names them, which is redundant but harmless. Combined with annotations covering safety and the schema covering all six parameters, an agent has everything needed to call it correctly; only pagination/truncation hints are missing.

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 schema already documents every parameter including defaults and the year/months interaction. The description's field list and category enumeration largely restate what the schema's enums provide, adding only the useful note that timestamps are Sydney time. Baseline 3 is appropriate.

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 ("List") and a precisely scoped resource ("ASX company announcements for a listed Australian company by ticker"), then enumerates the returned fields including the derived category taxonomy. An agent can separate it from asx_get_share_issues and asx_get_company without opening any 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?

The final sentence explicitly routes dilution questions to asx_get_share_issues, which is a real when-to-use-else signal. It stops short of stating when NOT to use this tool (e.g. when the user only knows a company name rather than a ticker), so it is clear but not exhaustive.

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.