Skip to main content
Glama

Capital Signal: ASX announcements

Market pulse

market_pulse
Read-onlyIdempotent

Counts and dollars over every row in a window, grouped by sector or industry group x week or month, for 'what is the market doing' questions by sector or over time. One call covers every row rather than a screen's first page, returned as paged cells (default 25 cells; nextCursor pages the rest; each page is kept under 30,000 characters). Families: dealing (director buys $, sales $, net $, trade counts; tax-on-vesting sales shown apart, not in net), guidance (upgrades/downgrades/reaffirmed/initiated/withdrawn, split by metricClass), raises (count, A$m sought and completed, median stated discount), ma (new bids, proposals, signed schemes, median premium), distress (administrations, receiverships, liquidations, credit-rating downgrades), holders (substantial-holder increases vs decreases by holder type, stock lending left out). Every cell carries examples: up to 3 rows behind it with symbol and docKey. Example: director buys vs sales by sector since 1 Sep -> groupBy='sector', families='dealing'. Results carry the caveats alongside the numbers. Free.

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": {
      "since": "<since>"
    },
    "name": "market_pulse"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMax cells per page, 1-100 (default 25). A heavy cell shrinks the page further so the response stays under 30,000 characters.
sinceYesEarliest date YYYY-MM-DD (required).
untilNoLatest date YYYY-MM-DD.
cursorNoNext page: the nextCursor from the previous response. A non-null nextCursor means more cells follow; null is the last page.
sectorNoOptional: one sector, industry group or tag.
groupByNoComma-separated: one of sector|industryGroup and/or one of week|month (default 'sector,week'). 'sector' alone = one row per sector for the whole window.
familiesNoComma-separated subset of dealing,guidance,raises,ma,distress,holders (default all).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Annotations already declare read-only, idempotent, non-destructive and closed-world, but the description adds substantial behavior beyond them: per-page cell limits and the 30,000-character cap, how heavy cells shrink pages, nextCursor semantics, that every cell carries up to 3 example rows with symbol and docKey, that caveats ship with results, and family-specific accounting rules (tax-on-vesting sales kept out of net, stock lending excluded from holder counts). This is exactly the extra disclosure the annotations do not supply.

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 core capability and the every-row-vs-first-page distinction are front-loaded, and nearly every clause carries information an agent needs (families, paging, examples, caveats). The single dense paragraph with semicolon-chained family definitions is harder to scan than a bulleted list and could be trimmed, but the content itself earns its place.

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?

A complex aggregation tool with seven parameters and no output schema, yet the description covers the return structure (paged cells, up to 3 exemplar rows per cell, caveats attached), pagination behavior, and every family's semantics. An agent has enough to call it correctly and interpret the response without additional documentation.

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, but the description adds meaning: it clarifies that families select subsets of the six listed families with per-family metric definitions, gives a concrete groupBy/families call example, and explains that 'sector' alone yields one row per sector for the whole window. It stops short of documenting limit/cursor/until syntax once more, which the schema already handles.

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?

A specific verb+resource ('counts and dollars over every row in a window') plus the exact grouping dimensions and the question type it answers. It also distinguishes itself from a screen-type sibling by stating 'One call covers every row rather than a screen's first page', so an agent can tell it apart from paginated screening tools without reading 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 Guidelines4/5

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

Clear usage context: 'what is the market doing' questions by sector or over time, with a worked example mapping ('director buys vs sales by sector since 1 Sep -> groupBy=sector, families=dealing'). It names no explicit alternative tool or exclusion condition, so the when-not-to-use half of the guidance is left to inference.

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