Skip to main content
Glama

Tidy Quid budget planners

UK budget check (50/30/20)

uk_budget_check
Read-onlyIdempotent

Free calculator for UK take-home pay: converts weekly, fortnightly or 4-weekly pay to an average month, splits it 50/30/20, sets aside yearly bills monthly, says how much of pay goes on essentials, and suggests the matching Tidy Quid planner plus the free Budget Starter. Arithmetic only, not advice. Stores nothing.

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": {
      "take_home_pay": "<take_home_pay>"
    },
    "name": "uk_budget_check"
  }
}

Input Schema

NameRequiredDescriptionDefault
goalNoOptional, e.g. 'Christmas', 'save for a wedding', 'energy bills'
annual_billsNoTotal of once-a-year bills (MOT, car tax, insurance, TV Licence, Christmas) in GBP
monthly_billsNoMonthly essentials: rent/mortgage, council tax, energy, food, transport, debts (GBP)
pay_frequencyNomonthly
self_employedNo
take_home_payYesPay after tax, NI and pension, in GBP, per pay period

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive, and closed-world, so the safety profile is covered. The description adds meaningful context beyond that: "Arithmetic only, not advice" sets expectation of deterministic computation rather than recommendations, and "Stores nothing" clarifies that no data persists despite accepting personal financial figures.

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 dense sentence front-loads the core purpose, followed by two short clauses for the scope disclaimers. The middle enumeration of outputs is long but each item maps to a distinct computed result, so it earns its space, though the list could be trimmed slightly.

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?

For a 6-parameter calculation tool with no output schema, the description covers what inputs mean conceptually, what is returned at a high level (monthly average, category splits, bill set-aside, essentials percentage, suggested planner), and the read-only non-persistent nature. Only the optional goal and self_employed parameters' effects are left unexplained.

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 coverage is 67%, with most fields self-documenting (take_home_pay explicitly defined as post-tax/NI/pension per pay period, annual_bills uses of MOT/car tax/Christmas are spelled out in the schema). The description adds the semantic link between pay_frequency and monthly averaging, but leaves goal and self_employed behavior unmentioned, so it only partly compensates for the coverage gap.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

"Free calculator for UK take-home pay" names a specific resource and operation, then enumerates exactly what it computes: frequency normalization, 50/30/20 split, annual-bill smoothing, essentials ratio, and planner recommendation. This is clearly distinguishable from uk_money_dates (date handling) and search_products.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description establishes the domain (UK pay, take-home) and the arithmetic framing, which implicitly tells an agent to use this over other budgeting tools, and mentions it suggests the matching Tidy Quid planner rather than doing product lookup itself. It does not explicitly say when to prefer it over recommend_planner or search_products, so exclusion guidance is incomplete.

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