Skip to main content
Glama

Taipei Ledger

Find a company

find_company
Read-onlyIdempotent

Find Taiwan-listed companies by stock code (2330, 2330.TW), English name, nickname (Foxconn, TSMC) or Chinese name (台積電). Returns code, names, board (TWSE or TPEx), industry and the Taipei Ledger page.

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": {
      "query": "<query>"
    },
    "name": "find_company"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
queryYes

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, destructiveHint=false and closed-world, so the safety profile is fully covered. The description adds real value beyond that by naming the returned fields and the possible board values (TWSE or TPEx). However, it says nothing about match behavior: whether name matching is fuzzy, what happens with multiple or zero matches, or how results are ordered – all relevant for a name-based lookup.

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 tight sentences, zero filler, and the accepted input formats are front-loaded with concrete examples before the return fields. Structure is efficient and readable.

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 spends its words on the return field list, which is exactly what an agent needs. For a simple two-parameter read tool this is nearly complete; the residual gaps are no-match/multi-match behavior and the meaning of limit.

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 0%, so the description carries the burden. It compensates well for the required 'query' parameter by spelling out four accepted input shapes with examples. The 'limit' parameter (default 10) is never mentioned, and the absence of a limit explanation reinforces the missing information about multiple-match ranking and result ordering.

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?

Specific verb plus resource: 'Find Taiwan-listed companies' with four concrete query formats (code, .TW suffix, English name/nickname, Chinese name) and an explicit return field list. The scope is unmistakable. It stops short of 5 because it never contrasts itself with the obvious sibling get_company, leaving the agent to infer that 'find' is the discovery path and 'get' the direct-retrieval path.

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 implied by the enumerated query forms – an agent can see this is the lookup-by-anything entry point – but there is no explicit when-to-use guidance, no exclusion ('use get_company when you already have an exact code'), and no prerequisites. Acceptable but leaves routing to inference.

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