Skip to main content
Glama

BRAINIAC Indirect Tax Calculations

UK VAT invoice content requirements check

indirect-tax_vat-invoice-requirements
Read-onlyIdempotent

Check a supplied invoice against HMRC Notice 700/21 full and simplified VAT invoice content rules and recompute arithmetic. Price $0.03 USDC. POST /api/v1/indirect-tax/vat-invoice-requirements. An unpaid call returns the x402 payment terms and does not run.

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": {
      "invoice": "<invoice>"
    },
    "name": "indirect-tax_vat-invoice-requirements"
  }
}

Input Schema

NameRequiredDescriptionDefault
typeNotype, string, one of full, simplified, auto. Required.auto
invoiceYesinvoice, object. Required.
supplierIsRetailerNosupplierIsRetailer, boolean. Required.

Output Schema

NameRequiredDescriptionDefault
typeNotype. String.
missingNomissing. Array.
sourcesNosources. Array.
warningsNowarnings. Array.
arithmeticNoarithmetic. Object.
limitationsNolimitations. Array.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already establish readOnly/idempotent/non-destructive/openWorld, and the description usefully adds behavior beyond them: it recomputes arithmetic rather than only checking fields, it is a paid endpoint at $0.03 USDC, and an unpaid call returns x402 payment terms without executing. That unpaid-call contract is exactly the kind of auth/payment disclosure the annotations cannot convey.

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 short sentences, front-loaded with the purpose and standard before the cost, endpoint, and payment caveat. Nothing is padded or repeated from the title.

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 tool with three top-level parameters, deep nested invoice objects, and a defined output schema, the description covers purpose, governing standard, arithmetic recomputation, and the payment gate. The only real gap is that it does not spell out what the caller must supply to satisfy each full/simplified mode, but the schema and output schema carry most of that burden.

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 schema already documents every field, and the description adds only a light gesture toward the type parameter by mentioning "full and simplified" rules. It does not explain how the default "auto" mode is resolved or which invoice fields are mandatory for each mode.

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?

States a specific verb (check) plus a specific resource (a supplied invoice) and the exact standard applied (HMRC Notice 700/21 full and simplified VAT invoice content rules), plus a secondary behavior (recompute arithmetic). This is clearly distinct from the sibling tools, which cover flat-rate schemes, OSS thresholds, MTD ITSA, and non-UK GST regimes.

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 description implies when to use it (you have an invoice and want a UK VAT content-compliance check), but gives no explicit when-not conditions and never names an alternative for adjacent questions such as flat-rate scheme applicability. The "auto" mode hint in the schema is not explained in prose.

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