Skip to main content
Glama

Read HKEx Filing

get_filing
Read-onlyIdempotent

Download one HKEx document by its URL and read, page through, or search its text.

``link`` must be an HKEx document URL from search_filings (host ``www1.hkexnews.hk``);
any other host is rejected. With ``extract=True`` (default) the response includes up to
30 ``tables`` and a window of extracted ``document_text``: ``max_chars`` characters
starting at ``offset``. Long reports return ``next_offset``; call again with it to read
the next window. Pass ``query`` to search the whole document instead: the response then
lists up to 20 case-insensitive matches with their offsets and surrounding text, plus
``match_count`` — use a match offset to read that part. Set ``extract=False`` for size
and content type only.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
linkYesHKEx document URL from a search_filings result (host www1.hkexnews.hk)
queryNoOptional text to find in the whole document; returns matches with offsets instead of a text window
offsetNoCharacter offset where the returned text window starts (use next_offset to page)
extractNoExtract text and tables; false returns size and content type only
max_charsNoMaximum characters of document_text to return in this window

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYesThe downloaded document, with text and tables when extract is true.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.9/5.0
Behavior5/5

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

Beyond the annotations (readOnly, idempotent, openWorld, non-destructive), it discloses host validation/rejection, the default extract behavior, the 30-table cap, the 20-match cap for queries, and the next_offset paging contract. These are concrete behavioral traits the annotations cannot express.

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?

Front-loaded purpose sentence followed by tightly scoped paragraphs, one per mode. The code-formatted parameter references make it scannable, and no sentence is redundant.

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?

Given an output schema exists, return-value documentation is not strictly required, yet the description still characterizes the response shape (tables, document_text, next_offset, matches). Combined with the annotations, nothing needed to invoke this correctly is missing.

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; however, the description adds real cross-parameter semantics the schema lacks — how offset/max_chars interact for windowing, and how query switches the response from a text window to match listings. It does not fully restate defaults, but it meaningfully enriches interpretation.

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?

Opens with a specific verb+resource ('Download one HKEx document by its URL') and enumerates the three modes of operation (read, page, search). This clearly distinguishes it from search_filings, which locates documents rather than retrieving them.

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?

Explicitly states the precondition that link must come from search_filings and that non-HKEx hosts are rejected, and it gives a decision rule for each mode: query to search, offset/next_offset to page, extract=False for metadata only. No alternative routing 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.