Skip to main content
Glama

Taipei Ledger

Taiwan-Japan links

get_japan_links
Read-onlyIdempotent

Links between Taiwan-listed companies and Japanese companies from Taiwanese (MOPS) and Japanese (EDINET) filings: Japanese subsidiaries and units, Japanese shareholders, equipment bought from or sold to Japanese firms, joint ventures. Give a Taiwan company, a Japanese company (name or TSE code, e.g. 'Tokyo Electron' or '8035'), or neither for the full list.

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_japan_links"
  }
}

Input Schema

NameRequiredDescriptionDefault
companyNo
japan_companyNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/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 value beyond that by disclosing data provenance (Taiwanese MOPS and Japanese EDINET filings) and the full scope of relationship types returned, which matters since there is no output schema. It stops short of noting result size, pagination, or empty-match behavior for the 'neither' case.

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 the core purpose, then a dense but efficient colon-delimited enumeration of link types, then the calling convention. No filler sentences; the enumeration is information-dense rather than padded.

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 two-optional-parameter, read-only, closed-world tool with no output schema, the description covers what is returned and how to invoke every parameter combination. Remaining gaps (result size limits, matching semantics, response shape) are comparatively minor.

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 0% and both parameters are undescribed in the schema, so the description carries the burden and does it well: it explains the Taiwan-side filter, that japan_company accepts either a name or a TSE code with worked examples ('Tokyo Electron', '8035'), and that omitting both yields the full list. It leaves unresolved whether inputs must be exact matches or accept partial names, and how the two filters combine.

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 ('Links between Taiwan-listed companies and Japanese companies') along with the two filing sources (MOPS, EDINET) and enumerates exactly which link types are returned: subsidiaries, shareholders, equipment trade, joint ventures. An agent can distinguish this from get_supply_chain or get_investments from the description alone.

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?

Explicitly describes the three invocation modes: pass a Taiwan company, pass a Japanese company (name or TSE code), or pass neither to get the full list. That is concrete when/how-to-call guidance, though it does not name any sibling tool or state exclusions against them.

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