Skip to main content
Glama

Asx Announcements

Asx Get Share Issues

asx_get_share_issues
Read-onlyIdempotent

Dilution view of a listed Australian company: ASX announcements that signal new or changed share capital - applications for quotation of securities (Appendix 2A), proposed issues (Appendix 3B), placements, share purchase plans, entitlement offers, unquoted securities (options and performance rights), cessations and buy-backs - with counts per category and per month. Classified from the announcement headline; share counts and prices are inside the linked PDF and are not extracted. Source: ASX company announcements.

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": {
      "year": 2025,
      "ticker": "LTR"
    },
    "name": "asx_get_share_issues"
  }
}

Input Schema

NameRequiredDescriptionDefault
yearNoFull calendar year instead of a rolling window, e.g. 2025
monthsNoLook-back window in months (default 6). Ignored when year is given.
tickerYesASX code, e.g. "BHP", "LTR", "PLS"

Output Schema

NameRequiredDescriptionDefault
caveatNo
eventsNo
sourceNo
tickerNo
windowNo
by_monthNo
data_as_ofNo
by_categoryNo
capital_eventsNo
total_announcements_in_windowNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, open-world behavior, and the description adds genuinely useful caveats beyond that: classification comes only from the headline, share counts and prices live in the linked PDF and are not extracted, and results are aggregated as counts per category and per month. That tells an agent how much to trust the output.

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 dense sentence, front-loaded with the purpose and the source, then the category list. The long enumeration earns its place by defining scope, though it makes the sentence heavy and pushes the data caveat to the tail.

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?

For a three-parameter, read-only, output-schema-backed tool, the definition covers purpose, scope, provenance, aggregation shape, and the key accuracy limitation (headline-only classification, no numbers extracted). An agent has everything needed to call it and interpret results 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 coverage is 100%, so the enum for months, the 'ignored when year is given' note, and the ticker example are all already documented in the schema. The description only loosely reinforces the 'per month' aggregation and adds no new meaning about parameter behavior.

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 states a specific subject ('Dilution view of a listed Australian company') and enumerates exactly which announcement types are counted (Appendix 2A, 3B, placements, SPPs, entitlement offers, unquoted securities, cessations, buy-backs). This scope narrowing implicitly separates it from the broader announcements sibling, though no alternative is named.

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 implied by the stated scope - you call it when you want capital-raising/dilution signals rather than a raw announcement feed - but there is no explicit when-to-use, when-not-to-use, or pointer to asx_get_announcements for the unfiltered case.

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.