Skip to main content
Glama

Taipei Ledger

Supply chain (US filings)

get_supply_chain
Read-onlyIdempotent

Supply-chain links between Taiwan-listed companies and US-listed companies, found in US annual reports (SEC 10-K / 20-F) and reviewed by the editor: who supplies whom, competitors, partners, each with the quoted sentence and the filing. Give a Taiwan company (code or name) or a US company name (e.g. 'NVIDIA', 'Apple'). relation: supplier, competitor or partner. Read each link as: a_name b_name (a is supplier of b).

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "company": "<company>"
    },
    "name": "get_supply_chain"
  }
}

Input Schema

NameRequiredDescriptionDefault
companyYes
relationNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/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 safety is covered. The description adds genuinely useful context beyond that: the data originates in US annual reports, has been editor-reviewed, and every link is accompanied by the supporting quoted sentence and filing — telling the agent the results are evidenced rather than inferred.

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?

Three compact sentences, front-loaded with what the data is before moving to inputs and the relation vocabulary. The direction-reading clause is slightly dense but every sentence carries information; there is no filler.

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?

With no output schema, the description still tells the agent what a result contains (counterparties, relation, quoted sentence, filing) and how to read its direction. For a two-parameter read-only lookup, that is sufficient to call and interpret it correctly.

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%, so the description carries the burden and mostly does: it explains that 'company' accepts either a Taiwan code/name or a US company name and that 'relation' is one of supplier, competitor, or partner. It also defines the direction convention (a_name <relation> b_name, a supplies b), which is essential for interpreting results. It does not say what happens when 'relation' is omitted despite its null default.

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?

The description names a specific resource (supply-chain links between Taiwan-listed and US-listed companies) and its provenance (SEC 10-K / 20-F filings, editor-reviewed), with the concrete payload each link carries: counterparties, relation type, quoted sentence, and filing. This clearly separates it from siblings like get_investments, get_japan_links, and search_filings without requiring 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 Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It tells the agent exactly what to supply — a Taiwan company code or name, or a US company name such as 'NVIDIA' or 'Apple' — and enumerates the allowed relation values. It stops short of stating when not to use it or naming a specific alternative tool for adjacent questions (e.g. general filing search).

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