Skip to main content
Glama

Cash needed to buy

buying_costs
Read-onlyIdempotent

Use this for the cash needed to buy one home: the deposit, stamp duty or its Scottish or Welsh equivalent, conveyancing, survey and mortgage fees, less the builder's stated cash offers that apply (for a home page address), against savings when given; and for a home, the monthly cost with the service charge and ground rent the builder states. Give a home page address, or a price and nation.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "buying_costs"
  }
}

Input Schema

NameRequiredDescriptionDefault
homeNoA home page address from a search: its price, nation and builder offers are used.
priceNo
nationNoWhere the home is. Scotland pays LBTT and Wales LTT; England and Northern Ireland stamp duty.
surveyNo
depositNo
savingsNo
mortgageNoBuying with a mortgage: mortgage fees are counted.
additional_homeNo
deposit_percentNo10 when no deposit is given.
first_time_buyerNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already declare this a read-only, idempotent, non-destructive, closed-world operation, so the safety profile is covered. The description adds useful calculation semantics — builder cash offers apply only when a home page address is supplied, and savings are netted 'when given' — but it says nothing about what happens when neither home nor price/nation is provided, how partial data is handled, or what the result payload looks like.

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

Conciseness3/5

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

The purpose is front-loaded and every clause carries information, but the second sentence is dense and tangled — 'less the builder's stated cash offers that apply (for a home page address), against savings when given' — requiring careful re-reading. A cleaner separation of the cash calculation from the monthly-cost calculation would help.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a 10-parameter calculation tool with no output schema, the description should more fully explain the return shape and the optional toggles. It does convey the main inputs and the two outputs (upfront cash and monthly cost), but leaves several parameters and the exact response format undocumented.

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 only 40%, so the description needs to compensate and it partially does: it explains home, price, nation, deposit, savings, and that builder offers come from the home record. However, it never mentions the survey, mortgage, additional_home, deposit_percent, or first_time_buyer toggles, leaving half the parameters to the bare 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 opens with a specific verb-and-resource framing: 'Use this for the cash needed to buy one home', and then enumerates the components (deposit, stamp duty/LBTT/LTT, conveyancing, survey, mortgage fees, builder offers, savings) plus the monthly cost view. That distinguishes it in substance from a pure stamp-duty or mortgage calculator, but it never names a sibling or explicitly contrasts itself with stamp_duty_calculator or affordability_calculator.

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?

It states an implied use case (cash needed to buy) and gives invocation-level guidance — 'Give a home page address, or a price and nation' — but offers no when-not guidance and no explicit alternatives. An agent must infer that stamp_duty_calculator is for duty-only questions rather than being told so.

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