Skip to main content
Glama
Sign In
Bounty-api

Bounty-api

by vncent786
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

sg_income_tax

Calculate Singapore individual income tax with progressive or flat rates. Get marginal breakdown, effective rate, and tax payable for residents and non-residents.

Instructions

Calculate Singapore individual income tax. Resident progressive rates (0-22%, YA 2024+). Non-residents: 15% flat or progressive. Returns marginal breakdown, effective rate, and tax payable. FREE

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": {
      "annual_income": "<annual_income>"
    },
    "name": "sg_income_tax"
  }
}

Input Schema

NameRequiredDescriptionDefault
reliefsNoTotal personal reliefs (earned income, spouse, child)
deductionsNoTotal deductions (CPF, expenses, donations)
is_residentNoTax residency status
annual_incomeYesGross annual income in SGD

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4/5.0
Behavior3/5

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

No annotations are provided, so the description must cover behavioral traits. It states the tool is free and returns marginal breakdown, effective rate, and tax payable, but does not disclose any side effects, rate limits, or prerequisites (e.g., valid income range). For a simple calculator, this is adequate but not comprehensive.

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?

The description is two sentences, front-loading the purpose and concisely summarizing rates and outputs with no extraneous information.

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?

Given no output schema, the description explains return values (marginal breakdown, effective rate, tax payable). It covers all four parameters implicitly through rate context, but lacks explicit mention of income limits or error handling. Overall, it is sufficiently complete for a straightforward calculation tool.

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

Parameters3/5

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

Schema description coverage is 100%, so the schema already describes each parameter. The description adds context about tax rates and residency, but does not provide additional semantics beyond the schema. Baseline of 3 is appropriate.

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 clearly states the tool calculates Singapore individual income tax, specifies rates for residents and non-residents, and lists return values. It distinguishes from sibling tools like sg_gst and sg_stamp_duty, which cover different tax types.

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?

The description indicates the tool is for Singapore income tax calculations, with rate details for residents and non-residents. While it doesn't explicitly state when not to use or list alternatives, the sibling context (e.g., sg_gst) makes the usage clear.

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

Deploy Server

Other Tools