Skip to main content
Glama

Taipei Ledger

Search announcements

search_filings
Read-onlyIdempotent

Material announcements (重大訊息) of Taiwan-listed companies, translated into English: title, summary, category and the Chinese subject. Search by words (English or Chinese, 3+ characters), company, category (e.g. 'Dividends', 'Contracts and orders', 'Investments and acquisitions') and how many days back (the archive starts 2026-11-01). Newest first.

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

Input Schema

NameRequiredDescriptionDefault
limitNo
queryNo
companyNo
categoryNo
since_daysNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, and closed-world, so the safety profile is covered. The description adds genuinely useful behavior: results are newest-first, content is English-translated, queries must be 3+ characters, and coverage starts 2026-11-01. It stops short of describing result volume or pagination.

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?

Front-loaded with what the tool returns, then the search axes, then the ordering guarantee. Dense with parentheticals but every clause carries information; nothing is redundant filler.

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 correctly compensates by naming the four returned fields and the sort order. For a zero-required-parameter, five-parameter search tool the remaining gap is minor: limit semantics and behavior on empty/oversized result sets.

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 description coverage is 0%, so the description must carry the load, and it explains query (English or Chinese, 3+ chars), company, category with three concrete category examples, and since_days as days-back with an archive start date. Only the limit parameter (default 20) is left unexplained.

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?

Names the specific resource (material announcements / 重大訊息 of Taiwan-listed companies) and the verb (search), and enumerates the returned fields (title, summary, category, Chinese subject). It is plainly distinct from siblings like get_revenue, find_company, or get_supply_chain without needing their schemas.

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?

The description implies when to use it by listing search axes and stating the archive begins 2026-11-01, but it never says when to prefer a sibling or what this tool cannot do. Usage guidance is present but inferred rather than explicit.

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