Skip to main content
Glama

Taipei Ledger

Investment announcements

get_investments
Read-onlyIdempotent

Asset purchases and disposals announced by Taiwan-listed companies (machinery and equipment, land and buildings, leases, shares of subsidiaries, capital injections), parsed from their filings, with the NT$ amount, place, counterparty and source link. Filter by company, asset_type (e.g. 'Machinery'), kind ('acquisition' or 'disposal'), days back and minimum NT$ amount. Largest 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": "get_investments"
  }
}

Input Schema

NameRequiredDescriptionDefault
kindNo
limitNo
companyNo
asset_typeNo
since_daysNo
min_amount_ntdNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior3/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 contributes provenance ('parsed from their filings') and ordering ('Largest first'), but says nothing about how the default limit of 25 truncates results or whether a way exists to page through the rest of a large result set — a real concern for a 'largest first' ranked list.

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?

Two dense sentences, front-loaded with the data source and payload, then filters, then ordering. The long asset-category parenthetical is long but earns its place by defining the asset_type domain; nothing is redundant.

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 helpfully names the returned fields (amount, place, counterparty, source link) and the sort order. Given six parameters and no schema documentation, the remaining gaps are the limit/pagination behavior and company-matching semantics — minor but non-trivial for a read tool with a low default limit.

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 compensate, and it largely does: it explains kind ('acquisition' or 'disposal'), asset_type with a concrete example ('Machinery'), days back, and minimum NT$ amount. Only 'limit' is never mentioned, and the matching mode for 'company' (ticker vs name, exact vs partial) remains ambiguous.

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+resource: 'Asset purchases and disposals announced by Taiwan-listed companies', enumerates the asset categories covered, and describes the payload fields (NT$ amount, place, counterparty, source link). This is distinguishable from siblings like search_filings or get_company without opening the schema.

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 by the described scope and filters ('Filter by company, asset_type, kind, days back and minimum NT$ amount'). There is no explicit when-to-use vs when-not guidance and no named alternative such as search_filings for raw filing text, so an agent must infer routing.

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