Skip to main content
Glama

Propely Singapore Property

Singapore seller net proceeds

calculate_seller_net_proceeds
Read-onlyIdempotent

Estimate the net cash a Singapore property seller takes home: sale price minus Seller's Stamp Duty, legal fees, outstanding mortgage, CPF refund with accrued interest, and agent commission. Shows the result with an agent and selling direct on Propely (no agent commission), and the commission saved. From Propely (propely.sg), the owner-direct condo marketplace in Singapore. Indicative figures, not legal or financial advice.

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": {
      "salePrice": "<salePrice>",
      "purchaseDate": "<purchaseDate>",
      "saleDate": "<saleDate>"
    },
    "name": "calculate_seller_net_proceeds"
  }
}

Input Schema

NameRequiredDescriptionDefault
saleDateYesIntended date of sale (must be after purchaseDate), as YYYY-MM-DD
legalFeesNoConveyancing legal fees in Singapore dollars (SGD)
salePriceYesExpected sale price in Singapore dollars (SGD)
cpfInterestNoCPF accrued interest if known; omit to estimate at 2.5% p.a. in Singapore dollars (SGD)
cpfPrincipalNoCPF principal used for the property, to be refunded in Singapore dollars (SGD)
purchaseDateYesDate the property was purchased, as YYYY-MM-DD
gstOnCommissionNoAdd 9% GST on the agent commission
commissionPercentNoAgent commission as a percent of the sale price
outstandingMortgageNoOutstanding home loan to be repaid on completion in Singapore dollars (SGD)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already cover safety (readOnlyHint, idempotentHint, openWorldHint=false), so the bar is lower. The description still adds real behavioral context beyond them: it discloses the return shape (results shown both with an agent and selling direct, plus the commission saved) and flags that figures are indicative and not legal/financial advice. It does not state CPF interest assumptions in the prose, but those live in the schema.

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?

Three sentences, front-loaded with the actual computation before the extras. The core sentence is dense and earns its place; the brand blurb ("From Propely (propely.sg), the owner-direct condo marketplace") is mild marketing that could be trimmed, and the disclaimer is justified.

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?

For a 9-parameter read-only calculator with 100% schema coverage and no output schema, the description compensates well: it names the deducted components, describes what the response contains (both scenarios and the commission saved), and sets expectations on accuracy. An agent has enough to invoke it correctly.

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% across all 9 parameters, with defaults, patterns, and ranges documented, so the schema carries the semantic burden and 3 is the baseline. The description's enumeration of cost components loosely maps to legalFees, outstandingMortgage, cpfPrincipal/cpfInterest, and commissionPercent, but adds no format or edge-case detail (e.g. how purchaseDate/saleDate drive SSD tenure) beyond the schema.

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 gives a specific verb ("Estimate") and a precise resource (net cash a Singapore property seller takes home), then enumerates the exact deductions: SSD, legal fees, outstanding mortgage, CPF refund with accrued interest, and agent commission. It is a clear purpose statement, but it never differentiates itself from the sibling calculate_ssd even though SSD is one of its own inputs, leaving an agent to infer the boundary.

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 scenario (a seller estimating proceeds) rather than stated. There is no when-to-use/when-not guidance and no routing to alternatives, despite heavy overlap with calculate_ssd and calculate_decoupling in the sibling set. It does explain that the output covers both the agent-assisted and owner-direct cases, which is mild contextual guidance.

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