Skip to main content
Glama

Twcompany By Ban

twcompany_by_ban
Read-onlyIdempotent

Full registration record for one Taiwanese company by its 統一編號 (8-digit Business Administration Number, the id printed on every Taiwanese invoice and used in government tender awards). Returns registered name, responsible person, authorised and paid-in capital, par value, registered address, registering authority, incorporation date and the date of the most recent registered amendment, sourced from Taiwan's Ministry of Economic Affairs company register. AUTHORITATIVE for resolving a Taiwanese tax/company number to the entity behind 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": {
      "ban": "22099131"
    },
    "name": "twcompany_by_ban"
  }
}

Input Schema

NameRequiredDescriptionDefault
banYesThe 8-digit 統一編號 / Business Administration Number, e.g. 22099131 (TSMC).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already cover read-only, idempotent and open-world behaviour, so the description's extra load is the data provenance (Ministry of Economic Affairs register) and the freshness signal ('date of the most recent registered amendment'). It says nothing about what happens when a BAN is not found or invalid, which is a real gap for a lookup keyed on a checksummed ID.

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 operation and the key, then the field inventory and provenance. The parenthetical gloss on 統一編號 is slightly long but every clause carries information the agent would otherwise have to guess.

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 compensates by enumerating the returned fields, and it names the upstream source. The only missing pieces are failure/empty-result behaviour and whether the record is a point-in-time snapshot, both relevant for an open-world external lookup.

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 100% and already documents the single ban field, so the baseline is 3; the description earns one extra point by explaining what the number actually is in practice (printed on every invoice, used in government tender awards), which helps the agent recognise the value in user input.

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?

States a specific verb (returns full registration record) and resource (one Taiwanese company) with the exact key (8-digit 統一編號). The 'by its 統一編號' framing implicitly separates it from twcompany_search_name, but no sibling is named explicitly, which is the one thing keeping it from a 5.

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?

'AUTHORITATIVE for resolving a Taiwanese tax/company number to the entity behind it' gives a clear use case and a trust claim, plus the invoice/tender-award context tells the agent where such numbers come from. It stops short of stating when NOT to use it or naming the name-search alternative.

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.