Skip to main content
Glama
narinthon-so

thailand-data-mcp

by narinthon-so

Thai Company Registry Lookup

thai_company_lookup
Read-onlyIdempotent

Verify a Thai company's legal status, registered capital, and address using its 13-digit DBD registration number for due diligence or contract checks.

Instructions

Look up a Thai company (juristic person) in the official DBD (Department of Business Development) registry by its 13-digit registration number.

Returns the official registry profile: Thai/English name, entity type, operating status, registration date, registered and paid-up capital (THB), business objective (bilingual, with TSIC-style code), and registered head-office address.

Args:

  • juristic_id (string): exactly 13 digits, e.g. "0107536000315"

Returns structured JSON: { "found": boolean, "company": { "juristicId": string, "nameTh": string, "nameEn": string, "type": string, // e.g. "บริษัทจำกัด" (Co., Ltd.), "บริษัทมหาชนจำกัด" (PCL) "status": string, // e.g. "ยังดำเนินกิจการอยู่" = still operating "registerDate": string, // YYYYMMDD "registeredCapitalBaht": number, "paidUpCapitalBaht": number, "objective": { "code": string, "textTh": string, "textEn": string }, "address": { ... } } | null, "fromCache": boolean, "attribution": string }

Examples:

  • Use when: verifying a Thai supplier/counterparty exists and is still operating (KYB / due diligence)

  • Use when: fetching official registered capital or address for a contract

  • Don't use when: you only have a company NAME — this tool requires the 13-digit ID (ask the counterparty or check their invoice/website footer)

Notes:

  • "found": false means the ID is not in the registry — it may be mistyped, or the entity may be a sole proprietor (not a juristic person).

  • Data is the live official registry, cached for 24h.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
juristic_idYes13-digit Thai juristic person registration number, e.g. '0107536000315'. Printed on invoices, contracts, and company documents; same number as the company's tax ID.
Behavior5/5

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

Annotations already declare read-only, idempotent, non-destructive. Description adds caching duration (24h), interpretation of 'found': false (sole proprietor or bad ID), and live source. No contradictions.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Well-structured with purpose, args, returns, examples, notes. Every sentence adds value. Front-loaded with primary verb and resource.

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?

Single parameter fully documented, full sample output provided despite no output schema. Covers all needed context for agent invocation.

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 covers parameter fully (pattern, example, source). Description adds context on where to find the ID (invoices, contracts) and reinforces the format. Just shy of 5 because schema already does most of the work.

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?

Description clearly states 'Look up a Thai company in official DBD registry by its 13-digit registration number.' Differentiates from siblings which are unrelated (address, holidays, provinces, VAT).

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

Usage Guidelines5/5

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

Explicitly provides use cases (KYB, due diligence, contract info) and a key don't-use-when (company name only, requiring 13-digit ID instead). Gives actionable guidance.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/narinthon-so/thailand-data-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server