Skip to main content
Glama

查台灣公司

lookup_supplier_company
Read-onlyIdempotent

查台灣公司:驗證統一編號檢查碼,並查經濟部公司登記狀態、代表人、資本額、地址。

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": "lookup_supplier_company"
  }
}

Input Schema

NameRequiredDescriptionDefault
banNo
nameNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is covered structurally. The description adds genuinely new context: the data comes from an external government registry (explaining the open-world flag) and a checksum is performed on the business number. It stays silent, however, on failure behavior when the checksum is invalid or the parameters are empty.

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?

A single front-loaded sentence that pairs the verb with the enumerated returned fields; nothing is redundant. It re-states the title at the start, which is mildly wasteful but harmless given the overall brevity.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/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 usefully enumerates the returned fields (registration status, representative, capital, address), which covers the return-value burden. The remaining gap is input-side: for a two-optional-parameter lookup with no schema documentation, an agent cannot tell which identifier to pass or how to combine them.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% and the description never discusses the two parameters by name. It implies that the 統一編號 is the input being checksum-validated (mapping loosely to `ban`) and that a company can be located by name (`name`), but it does not state that both are optional, whether either alone suffices, or what format each accepts. With zero schema coverage, more compensation was needed.

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?

The description names a specific verb and resource (look up a Taiwan company) and enumerates what it returns: tax-ID checksum validation plus MOEA registration status, representative, capital and address. That is far more specific than the bare name/title, though it does not explicitly separate itself from the sibling check_tax_registration, which plausibly overlaps on business-number verification.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

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

There is no when-to-use or when-not-to-use guidance, no routing to alternatives such as check_tax_registration, and no statement of prerequisites (e.g. that at least one of ban/name must be supplied, or which to prefer). The agent must infer the invocation context entirely from the purpose statement.

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