Skip to main content
Glama

BRAINIAC Indirect Tax Calculations

UK VAT Flat Rate Scheme percentage and VAT due

indirect-tax_uk-vat-flat-rate
Read-onlyIdempotent

Return the HMRC Flat Rate Scheme percentage for a business type and date (including limited-cost and first-year discount) and compute VAT due on VAT-inclusive turnover. Price $0.02 USDC. POST /api/v1/indirect-tax/uk-vat-flat-rate. An unpaid call returns the x402 payment terms and does not run.

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": "indirect-tax_uk-vat-flat-rate"
  }
}

Input Schema

NameRequiredDescriptionDefault
dateNodate, string. Optional.
listNolist, boolean. Optional.
businessTypeNobusinessType, string. Optional.
periodMonthsNoperiodMonths, integer. Optional.
goodsCostPenceNogoodsCostPence, integer. Optional.
firstYearOfRegistrationNofirstYearOfRegistration, boolean. Optional.
periodTurnoverForLcbPenceNoperiodTurnoverForLcbPence, integer. Optional.
vatInclusiveTurnoverPenceNovatInclusiveTurnoverPence, integer. Optional.

Output Schema

NameRequiredDescriptionDefault
rateNorate. Number.
sourcesNosources. Array.
baseRateNobaseRate. Number.
limitationsNolimitations. Array.
vatDuePenceNovatDuePence. Number.
limitedCostBusinessNolimitedCostBusiness. Boolean.
firstYearDiscountAppliedNofirstYearDiscountApplied. Boolean.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior5/5

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

Annotations already declare readOnly, openWorld, idempotent, and non-destructive behavior, but the description adds the paid-call model: $0.02 USDC, POST endpoint, and that an unpaid call returns x402 payment terms and does not run. That is exactly the kind of auth and failure behavior an agent needs before invoking. It does not discuss rate limits, but none are indicated.

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

Conciseness5/5

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

Three sentences, front-loaded with the calculation, then price/endpoint, then payment failure behavior. No filler; every sentence adds selection or invocation context. Structure is clear.

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 an 8-param tool, the description covers the main calculation, discounts, and payment failure, while annotations and output schema cover safety and returns. The remaining gap is that obscure optional params such as list and periodMonths are not explained, but the schema at least names them. Overall it is complete enough, not exhaustive.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so baseline is 3, but the description adds meaning: business type, date, VAT-inclusive turnover, and first-year/limited-cost discounts map to key inputs. It still leaves list, periodMonths, and the two LCB pence parameters largely unexplained. That puts it above baseline but short of full parameter guidance.

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?

The description states a specific verb ('Return'/'compute') and resource ('HMRC Flat Rate Scheme percentage' and 'VAT due on VAT-inclusive turnover'). The UK flat-rate domain is distinct from the sibling tax tools, so an agent can identify it without opening the schema. It also scopes the calculation to business type/date and discounts.

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 explicit when-to-use, when-not-to-use, or alternative tool guidance. The purpose implies it is for UK VAT Flat Rate Scheme calculations, but an agent must infer that from the verb and resource. No prerequisites beyond payment are stated.

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