mythaitaxes-mcp
Server Details
Free Thai personal income tax (PIT) calculator for salaried employees, from mythaitaxes.com.
- Status
- Healthy
- Last Tested
- Transport
- Streamable HTTP
- URL
Glama MCP Gateway
Connect through Glama MCP Gateway for full control over tool access and complete visibility into every call.
Full call logging
Every tool call is logged with complete inputs and outputs, so you can debug issues and audit what your agents are doing.
Tool access control
Enable or disable individual tools per connector, so you decide what your agents can and cannot do.
Managed credentials
Glama handles OAuth flows, token storage, and automatic rotation, so credentials never expire on your clients.
Usage analytics
See which tools your agents call, how often, and when, so you can understand usage patterns and catch anomalies.
Tool Definition Quality
Average 4.1/5 across 1 of 1 tools scored.
Only one tool exists, so no ambiguity between tools.
Single tool follows a clear verb_noun pattern, no inconsistency.
One tool is too few for a server named 'mythaitaxes-mcp', suggesting a narrow scope that likely leaves many tax-related operations uncovered.
The tool only handles salaried employee annual income tax, missing other tax types (e.g., corporate, VAT, withholding) that the server name implies.
Available Tools
1 toolcalculate_thai_annual_income_taxCalculate Thai Annual Personal Income TaxAInspect
Calculates Thailand personal income tax (PIT) for a salaried employee for a tax year, using current progressive tax brackets, standard allowances, and common deductions (social security, insurance, retirement funds, donations). Returns taxable income, tax owed, effective rate, and refund/amount owed against tax already withheld. Source: mythaitaxes.com.
| Name | Required | Description | Default |
|---|---|---|---|
| rmf | No | Retirement Mutual Fund contribution, max deductible 500,000 THB. | |
| ssf | No | Super Savings Fund contribution, max deductible 200,000 THB. | |
| donations | No | Charitable donations, capped at 10% of income after allowances. | |
| pensionFund | No | Max deductible 500,000 THB. | |
| taxWithheld | No | Tax already withheld by the employer this year, used to compute refund vs. amount owed. | |
| annualIncome | Yes | Total annual gross income in THB, before any deductions. | |
| lifeInsurance | No | Max deductible 100,000 THB. | |
| maritalStatus | No | single | |
| providentFund | No | Max deductible 500,000 THB. | |
| isAge65OrOlder | No | Adds the 190,000 THB senior allowance. | |
| healthInsurance | No | Max deductible 25,000 THB. | |
| numberOfParents | No | Dependent parents supported (30,000 THB each, max 4). | |
| numberOfChildren | No | ||
| spouseHasNoIncome | No | True if married and the spouse has no income (unlocks the 60,000 THB spouse allowance). | |
| childrenBornOnOrAfter2018 | No | 2nd-or-later children born in 2018 or after qualify for a doubled (60,000 THB) allowance. | |
| socialSecurityContribution | No | Annual social security fund contribution, max deductible 10,500 THB. |
Tool Definition Quality
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full burden. It discloses that calculation uses current tax brackets and common deductions, and mentions the source. However, it does not state whether the calculation is an estimate or based on official law, nor does it describe limitations (e.g., only for salaried income). Overall, it is mostly transparent but could be more explicit.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single sentence plus a source citation. It is concise and front-loaded with the main action. While not structured with bullet points, it is efficient and covers the essentials without unnecessary words. Slight improvement could be splitting into multiple sentences for clarity.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given 16 parameters (only one required), no output schema, and no siblings, the description provides a good overview. It lists the output fields and cites the source. However, it does not explain the calculation methodology, such as progressive tax brackets or order of deductions. It is complete enough for a typical user but could be enhanced with more detail.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 88%, meaning most parameters are already described in the schema. The description adds high-level categories (social security, insurance, retirement funds, donations) but does not provide additional details beyond what is in the schema. With high coverage, the baseline is 3, and the description adds minimal extra value.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states it calculates Thailand personal income tax for a salaried employee, using current brackets, allowances, and deductions. It specifies the outputs: taxable income, tax owed, effective rate, and refund/amount owed. There are no sibling tools to differentiate, but the purpose is precise and unambiguous.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description implies it is for a salaried employee in a tax year, using standard deductions. It does not explicitly mention when not to use it or provide alternatives, but since there are no sibling tools, the lack of exclusions is acceptable. The source citation adds credibility but does not replace usage guidance.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Claim this connector by publishing a /.well-known/glama.json file on your server's domain with the following structure:
{
"$schema": "https://glama.ai/mcp/schemas/connector.json",
"maintainers": [{ "email": "your-email@example.com" }]
}The email address must match the email associated with your Glama account. Once published, Glama will automatically detect and verify the file within a few minutes.
Control your server's listing on Glama, including description and metadata
Access analytics and receive server usage reports
Get monitoring and health status updates for your server
Feature your server to boost visibility and reach more users
For users:
Full audit trail – every tool call is logged with inputs and outputs for compliance and debugging
Granular tool control – enable or disable individual tools per connector to limit what your AI agents can do
Centralized credential management – store and rotate API keys and OAuth tokens in one place
Change alerts – get notified when a connector changes its schema, adds or removes tools, or updates tool definitions, so nothing breaks silently
For server owners:
Proven adoption – public usage metrics on your listing show real-world traction and build trust with prospective users
Tool-level analytics – see which tools are being used most, helping you prioritize development and documentation
Direct user feedback – users can report issues and suggest improvements through the listing, giving you a channel you would not have otherwise
The connector status is unhealthy when Glama is unable to successfully connect to the server. This can happen for several reasons:
The server is experiencing an outage
The URL of the server is wrong
Credentials required to access the server are missing or invalid
If you are the owner of this MCP connector and would like to make modifications to the listing, including providing test credentials for accessing the server, please contact support@glama.ai.
Discussions
No comments yet. Be the first to start the discussion!