Skip to main content
Glama

Capital Signal: ASX announcements

Filing text

filing_text
Read-onlyIdempotent

Full extracted text of one filing, one section at a time, identified by a doc_key from a search result, profile or event row. Returns headline, date, symbol, page, whether more sections exist and, for a long section, whether more text follows. Suited to reading a whole announcement rather than a snippet. 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": {
      "doc_key": "<doc_key>"
    },
    "name": "filing_text"
  }
}

Input Schema

NameRequiredDescriptionDefault
offsetNoCharacter offset within the section's text for long sections (default 0). The response's nextOffset pages the rest.
doc_keyYesFiling id, e.g. '2924-03102366-2A1678426'.
sectionNo0-based section index (default 0).

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 establish read-only, idempotent, closed-world and non-destructive, and the description adds real behavioral context on top: section-at-a-time retrieval, an offset mechanism for long sections, the returned fields (headline, date, symbol, page, more-sections and more-text flags) and the fact that it is free. That is meaningful disclosure beyond the structured hints.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two sentences, front-loaded with what is returned and how it is paged, then the usage cue. The terse 'Free.' earns its place as a cost signal rather than padding.

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-shape burden and does so well, plus paging and cost. It leaves out error behavior for an invalid doc_key or section index and any note on text formatting/cleanup, which are the remaining gaps for a read tool of this kind.

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 linkage the schema cannot: doc_key must come from a prior search/profile/event result, and section/offset paging is described as a coherent walk (response's nextOffset pages the rest). The mutual relationship between section and offset is clarified rather than merely repeated.

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 and resource — returns the full extracted text of one filing, one section at a time — and pins down the identifier's provenance (a doc_key from a search result, profile or event row). It also implicitly separates itself from snippet-returning search tools by noting it is 'Suited to reading a whole announcement rather than a snippet'.

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?

'Suited to reading a whole announcement rather than a snippet' gives a clear selection criterion for when this tool is the right one, and naming the doc_key sources tells the agent where the input must come from. It stops short of explicitly naming or excluding a sibling tool for the snippet case, so the routing is clear but not fully closed.

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