UK Stamp Duty Land Tax (SDLT) calculation with full breakdown.
| Name | Required | Description | Default |
|---|---|---|---|
| price | Yes | ||
| non_resident | No | ||
| first_time_buyer | No | ||
| additional_property | No |
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Changes observed during successful MCP inspections. Dates show when Glama detected each change.
Input schema / properties / additional_property / defaultPrevious value: -trueNew value: +falseInput schema / properties / additional_property / descriptionRemoved value: -"True if buying additional property (+5% surcharge)"Input schema / properties / first_time_buyer / descriptionRemoved value: -"True for first-time buyer relief (up to £300k nil rate)"Input schema / properties / non_resident / descriptionRemoved value: -"True if buyer not UK resident (+2% surcharge)"Input schema / properties / price / descriptionRemoved value: -"Purchase price in £"Input schema / properties / additional_property / descriptionPrevious value: -"Buying an additional property (+5% surcharge)"New value: +"True if buying additional property (+5% surcharge)"Input schema / properties / first_time_buyer / descriptionPrevious value: -"First-time buyer relief (up to 300k nil rate)"New value: +"True for first-time buyer relief (up to £300k nil rate)"Input schema / properties / non_resident / descriptionPrevious value: -"Non-UK resident (+2% surcharge)"New value: +"True if buyer not UK resident (+2% surcharge)"Input schema / properties / price / descriptionPrevious value: -"Purchase price in GBP"New value: +"Purchase price in £"Output schema / (root)Previous value: -nullNew value: +{
+ "additionalProperties": true,
+ "type": "object"
+}Input schema / properties / additional_property / descriptionPrevious value: -"True if buying additional property (+5% surcharge)"New value: +"Buying an additional property (+5% surcharge)"Input schema / properties / first_time_buyer / descriptionPrevious value: -"True for first-time buyer relief (up to £300k nil rate)"New value: +"First-time buyer relief (up to 300k nil rate)"Input schema / properties / non_resident / descriptionPrevious value: -"True if buyer not UK resident (+2% surcharge)"New value: +"Non-UK resident (+2% surcharge)"Input schema / properties / price / descriptionPrevious value: -"Purchase price in £"New value: +"Purchase price in GBP"Input schema / properties / additional_property / descriptionAdded value: +"True if buying additional property (+5% surcharge)"Input schema / properties / first_time_buyer / descriptionAdded value: +"True for first-time buyer relief (up to £300k nil rate)"Input schema / properties / non_resident / descriptionAdded value: +"True if buyer not UK resident (+2% surcharge)"Input schema / properties / price / descriptionAdded value: +"Purchase price in £"Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
The readOnlyHint annotation already indicates a safe, non-mutating operation, so the description does not need to repeat that. The phrase 'full breakdown' hints at detailed output, but no further behavioral traits (e.g., rate basis, jurisdiction limits) are disclosed. There is no contradiction with the annotation.
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, front-loaded sentence that efficiently conveys the tool's purpose without unnecessary words. It is appropriately concise for a tool with a straightforward function.
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 the tool has four parameters with zero schema descriptions, the description is under-specified. It does not explain the input parameters or any regional nuances (e.g., SDLT applies to England/NI only). While an output schema exists and covers return values, the lack of parameter context makes the description incomplete for accurate invocation.
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 0%, and the description does not compensate by explaining any parameters. While parameter names like 'non_resident' and 'first_time_buyer' are somewhat self-explanatory, the description provides no additional meaning, such as expected units or how booleans affect the calculation.
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 the tool calculates UK Stamp Duty Land Tax with a full breakdown, using a specific verb ('calculation') and a distinct resource. This differentiates it from sibling tools that perform searches or comparisons.
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 usage for SDLT calculations but provides no explicit guidance on when to use this tool over alternatives, nor does it mention any exclusions or prerequisite conditions. The context of sibling tools (all UK property-related) makes the purpose somewhat clear, but explicit usage direction is missing.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
EPC coverage is split across property_epc, property_epc_summaries, epc_certificate, and the deprecated property_epc_search, but each has a distinct role (aggregate lookup, candidate list, direct certificate, legacy). Land Registry data is similarly split between ppd_transactions and property_comps with clear output differences; no two tools are truly interchangeable.
Names are readable and consistently lowercase snake_case, but they mix resource nouns (epc_certificate, stamp_duty), prefixed nouns (property_epc_summaries, rightmove_listing), and noun-verb forms (company_search, planning_search). The 'search' suffix is used for different actions, and there is no uniform verb_noun pattern across the set.
14 tools is within the appropriate range for a multi-source property data API. The count is slightly padded by the deprecated property_epc_search and the narrowly scoped planning_search/company_search, but most tools cover distinct data products.
The set covers the core property workflows: Rightmove listing discovery/detail, EPC search/detail, Land Registry transactions/comps, yield/rent analysis, stamp duty, and planning portal lookup. Minor gaps exist (no planning application details, no property-level title/ownership lookup), but agents can complete common research tasks without dead ends.