Skip to main content
Glama

用統編查公司或商號

lookup_company
Read-onlyIdempotent

用 8 碼統一編號查一家公司或商號:組織別、縣市、設立日、營業項目(稅籍)、公司的稅籍地址與資本額、最近的官方登記事件(新成立、解散、停業、登記異動)、同地址的其他營業人數量。個人名義的商號(獨資、合夥)只給名稱、縣市、行業與設立年月。不提供負責人與董監事,也不評分。

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": {
      "tax_id": "<tax_id>"
    },
    "name": "lookup_company"
  }
}

Input Schema

NameRequiredDescriptionDefault
tax_idYes8 碼統一編號,例如 22099131

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior5/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, but the description adds substantial context they cannot carry: the conditional return shape for sole proprietorships and partnerships (name, city, industry, establishment month only), and explicit data gaps (no responsible person, no directors/supervisors, no scoring). An agent knows before calling that results may be partial depending on entity type.

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 paragraph that opens with the verb and identifier, then lists returns, then the exception case, then exclusions. Dense but every clause carries information; only the parenthetical event list is slightly heavier than needed.

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?

There is no output schema, so the description must describe return values itself, and it does so field by field, including the reduced payload for personal-name businesses. For a single-parameter read tool with annotation coverage, nothing an agent needs to call it correctly is missing.

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 there is only one parameter, so the baseline is 3. The description nonetheless adds real meaning: it pins the value to exactly 8 digits, resolving the ambiguity created by the schema allowing 8–12 characters, and the example format is consistent with the schema's stated example.

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 verb and resource ('用 8 碼統一編號查一家公司或商號') and then enumerates exactly which fields come back (organization type, city, establishment date, tax-registration business items, address, capital, recent registration events, co-located business count). That level of specificity makes it unmistakable against siblings such as check_tax_id or search_companies_by_name without opening 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 Guidelines3/5

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

Usage is implied by the input requirement — it only works when the caller already holds an 8-digit tax ID — and the description rules out some scope ('不提供負責人與董監事,也不評分'). But it never routes the agent among alternatives (e.g., name-based search when no tax ID is known, or check_tax_id for validation), so the when-to-use decision is left 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