Skip to main content
Glama

Taiwan Search Securities

taiwan_search_securities
Read-onlyIdempotent

Find a Taiwan-listed security by company name, English abbreviation or numeric code across both the TWSE main board and the TPEx OTC board. Returns code, Chinese name, English abbreviation, market and sector, the lookup that turns "Foxconn" or "鴻海" into 2317 before pricing it.

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "query": "TSMC"
    },
    "name": "taiwan_search_securities"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum matches to return, 1-100. Default 20.
queryYesCompany name, English abbreviation, or numeric code. Partial matches work.
marketNoRestrict to one board. Default all.

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 establish read-only, idempotent, non-destructive, open-world behavior, so the description's job is lighter, and it adds the result shape (code, Chinese name, English abbreviation, market, sector) and cross-board coverage, which the annotations do not. It omits ranking order, tie-breaking between similar names, and how partial matches are prioritized.

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 sentences, front-loaded with the core action and scope, with no padded marketing language. The second sentence is slightly run-on and mixes a return-value list with a usage aside, but nothing is wasted.

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, describing the returned fields is genuinely necessary and is done here; all three parameters are already covered by the schema and one example set. What's missing is disambiguation behavior when multiple companies match or how results are ordered under the 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 100% and every parameter (query, market, limit) is documented there with defaults and enum values. The description's mention of name/abbreviation/code and partial matching restates the schema rather than extending it, so baseline 3 applies.

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?

Uses a specific verb ('Find') on a specific resource ('a Taiwan-listed security') and pins down identifier types (company name, English abbreviation, numeric code) and board scope (TWSE main board plus TPEx OTC). That scope cleanly separates it from quote/valuation siblings, which take a code rather than resolve one.

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?

The closing clause, 'the lookup that turns "Foxconn" or "鴻海" into 2317 before pricing it,' gives clear situational guidance: call this first to resolve a name into a code. It does not name the specific sibling to follow with or state exclusions, so it falls short of the top score.

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.