Skip to main content
Glama

Kobo Terminal NGX

Corporate disclosures

get_disclosures
Read-onlyIdempotent

NGX corporate filings: financial statements, board meeting notices, dividend declarations, director dealings, AGM notices and more, with links to the original PDFs. Plan: Starter+.

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": "get_disclosures"
  }
}

Input Schema

NameRequiredDescriptionDefault
typeNoFilter by submission type, e.g. Financial Statements
limitNoNumber of filings, or "all". Example: 20
symbolNoFilter by ticker. Example: MTNN
companyNoFilter by company name

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is covered structurally. The description adds two useful behavioral facts beyond that: filings link out to original PDF documents, and access is gated to the Starter plan or above. It omits response size behavior, ordering, and how the 'all' limit value behaves.

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-loads the resource and its contents, then closes with the access tier. Nothing is redundant, though the 'and more' tail is vague and the plan note is tacked on rather than integrated.

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?

For a read-only list tool with a fully documented four-parameter schema and no output schema, the description covers subject matter, return form (PDF links), and entitlement level. Minor gaps remain around result ordering, default limit, and how this differs from the dividend-calendar and insider-dealing tools.

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 description coverage is 100%, so every parameter is already documented with examples in the schema. The description only implies that the enumerated document types map to the 'type' filter and adds no syntax, default, or interaction details beyond the schema — the baseline 3 applies.

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 names a concrete resource (NGX corporate filings) and enumerates the covered document types — financial statements, board meeting notices, dividend declarations, director dealings, AGM notices — plus the return form (links to original PDFs). It does not distinguish itself from siblings with overlapping scope such as get_dividend_calendar or get_insider_dealings, so an agent must infer the boundary.

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 only implied: an agent can infer this is the tool for browsing corporate filings and the 'Plan: Starter+' note communicates a subscription prerequisite. There is no explicit statement of when to prefer it over the dividend or insider-dealing siblings, and no exclusions or pagination guidance.

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