Skip to main content
Glama

Calculate tax on savings interest

calculate_savings_interest_tax
Read-only

Calculate UK tax on savings interest for a tax year, given the interest, any tax already deducted and other income: the starting rate for savings, the Personal Savings Allowance and the tax due.

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": {
      "grossInterest": "<grossInterest>"
    },
    "name": "calculate_savings_interest_tax"
  }
}

Input Schema

NameRequiredDescriptionDefault
taxYearNoUK tax year, e.g. "2026-27". Defaults to the current one.
otherIncomeNoOther taxable income
grossInterestYesSavings interest in the year
taxDeductedAtSourceNoTax already deducted from the interest

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds real behavioral value by naming what is computed (starting rate for savings, Personal Savings Allowance, tax due) and which inputs drive it, notably that other income and tax already deducted affect the result — information no structured field supplies, since there is no output 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?

A single front-loaded sentence that names the operation, the tax year scope, the inputs and the outputs. The trailing colon list is slightly dense but every element earns its place by previewing the computed components.

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?

With no output schema, the description carries the burden of previewing returns, and it does so by naming the three computed components. Combined with the read-only annotations and a fully documented input schema, an agent has enough to call this correctly; only explicit alternative-tool routing is missing.

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 every parameter is already documented in the schema with bounds and a default for taxYear. The description restates gross interest, tax deducted and other income without adding format, band or interaction semantics, so the baseline 3 applies.

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 and resource ("Calculate UK tax on savings interest for a tax year") plus the inputs it consumes, so an agent can tell it apart from calculate_dividend_tax or calculate_rental_income_tax. It stops short of explicitly naming the sibling calculators or the boundary cases where they would be preferred, so it is clear but not routed.

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?

There is no when-to-use or when-not-to-use guidance and no mention of alternatives among the many calculate_* siblings. The list of inputs implies a calculation context, but an agent gets no explicit condition for selecting this tool over calculate_tax_on_multiple_incomes or the other income-tax calculators.

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.