Skip to main content
Glama
Sign In
Bounty-api

Bounty-api

by vncent786
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

sg_cpf_housing

Calculate CPF Ordinary Account accumulation for housing use. Input monthly income and age to see monthly OA contribution and projected 3-year and 5-year balances.

Instructions

Estimate CPF Ordinary Account (OA) accumulation for housing use. Shows monthly OA contribution by age band, 3-year and 5-year projected balances at 2.5% interest. 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": {
      "monthly_income": "<monthly_income>",
      "age": "<age>"
    },
    "name": "sg_cpf_housing"
  }
}

Input Schema

NameRequiredDescriptionDefault
ageYesCurrent age (16-65)
monthly_incomeYesGross monthly income in SGD
existing_oa_balanceNoExisting CPF OA balance

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.2/5.0
Behavior2/5

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

With no annotations, the description must disclose behavioral traits. It mentions the interest rate but omits assumptions, limitations (e.g., CPF contribution caps, constant income), and whether it is read-only. This is insufficient for a tool that performs sensitive calculations.

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 with no wasted words. It front-loads the purpose and efficiently lists outputs. The 'FREE' tag is minor but does not detract.

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 the tool's simplicity (3 parameters, no output schema), the description adequately covers outputs and interest rate. However, it lacks details on contribution calculation rules and assumptions, so it is not fully complete.

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?

The schema covers all parameters (100% coverage). The description adds that age is used for banding and mentions projections, but does not elaborate on how each parameter affects the output. Baseline 3 is appropriate as schema does the heavy lifting.

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 clearly states the tool estimates CPF OA accumulation for housing, specifying outputs like monthly contribution and projected balances. It is specific about the verb and resource, though it does not explicitly differentiate from sibling tools like sg_affordability.

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?

No guidance is provided on when to use this tool versus alternatives such as sg_affordability or sg_stamp_duty. The context is implied but lacks explicit when-to-use or when-not-to-use instructions.

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