Skip to main content
Glama

UK Data: UK business calculators

stamp_duty

Read-onlyIdempotent

SDLT on a property purchase in England or Northern Ireland: standard, first-time buyer, additional property, or non-residential. (cost: 1 credit)

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": "stamp_duty"
  }
}

Input Schema

NameRequiredDescriptionDefault
priceNonumber, required
buyerTypeNostandard|first_time|additional
residentialNoboolean, default true

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, so the safety profile is covered. The description usefully adds the 1-credit cost, but says nothing about what is returned (e.g., a tax breakdown vs a single figure) or which rate bands/regime version is applied.

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?

A single compact sentence with the jurisdiction constraint front-loaded and the credit cost tucked into a parenthetical. No wasted words, though it reads as a fragment rather than stating the action.

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 3-parameter read-only calculator with full schema coverage and no output schema, the description is adequate but leaves gaps: it does not say what the result looks like, whether price accepts formatted strings, or how edge cases (e.g., non-UK purchases) are handled.

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 baseline is 3. The description does add light semantic mapping — 'non-residential' corresponds to the residential flag being false, and first-time/additional map to buyerType — but it never explicitly links these labels to the parameter names, so the added value is modest.

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?

Names the specific tax and resource (SDLT on a property purchase) and enumerates the four scenarios it handles, which distinguishes it from the generic 'calculate' sibling. The action verb (compute/estimate) is only implied by the noun phrase, keeping it short of a 5.

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?

The geographic scope (England or Northern Ireland) implicitly tells the agent this is not for Scotland or Wales, and the listed scenarios imply when it applies. There is no explicit guidance on when to prefer this over the sibling 'calculate' tool, and no stated preconditions.

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