Skip to main content
Glama

Capital Signal: ASX announcements

Capital thread

capital_thread
Read-onlyIdempotent

Raise lifecycles for an ASX company: every capital raise it announced, with announced vs completed amounts and both filings, and percent taken. With a symbol, the full raise ledger for one company; without a symbol, a market-wide scan for institutional placements that closed short. Not suited to retail entitlement offers or SPPs, whose shortfalls are routine rather than findings. Free.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

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

Input Schema

NameRequiredDescriptionDefault
limitNoMax rows (default 25, max 200; responses are capped at 30,000 characters).
symbolNoOptional ticker — omit to scan the whole market for failed placements.
sinceDaysNoScan only: how far back to look (default 730).
minPctTakenNoScan only: flag placements that closed below this percent of announced (default 80).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already cover read-only, idempotent, non-destructive, and closed-world behavior, so the description's job is supplementary. It adds cost information ('Free') and describes what the rows contain (announced vs completed amounts, both filings, percent taken), which the annotations do not. It does not discuss response size limits or ordering, though the schema notes the 30,000-character 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?

Two dense sentences plus a short exclusion clause; the mode split is front-loaded and nothing is filler. Slightly heavy clause packing (four data items in one sentence) costs a point on readability without wasting words.

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 carries the return-value burden and does so by enumerating the fields returned and both modes. It leaves the definition of 'closed short' to the minPctTaken default in the schema, which is reasonable, and defaults/limits are documented there.

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 100%, so the baseline is 3; the description earns extra credit by explaining the semantic consequence of omitting or supplying `symbol` (per-company ledger vs market-wide scan) and by framing the scan around failed placements, which is the meaning behind minPctTaken and sinceDays.

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?

The description names a specific resource and output ('every capital raise it announced, with announced vs completed amounts and both filings, and percent taken') for a specific market (ASX), and explicitly splits the tool into two modes keyed on whether a symbol is supplied. An agent can tell this apart from generic filing or screener siblings without opening the schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

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

It states both modes' conditions explicitly ('With a symbol, the full raise ledger for one company; without a symbol, a market-wide scan') and gives a clear exclusion ('Not suited to retail entitlement offers or SPPs, whose shortfalls are routine rather than findings'), including the reason the exclusion exists.

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.

Resources