Skip to main content
Glama

VAT summary for a period

get_vat_summary
Read-onlyIdempotent

Use this when the user asks how much VAT they owe or can reclaim for a period, their output or input VAT, or the figures for their next VAT return from their records. VAT figures for one VAT period of the business, as the VAT report page shows them: sales and output VAT, credit notes, input VAT, reverse charge, net VAT, counts, breakdowns, the filing deadline and whether the period is marked filed. It is a summary of the user's records in Fatura Go, not a filed VAT return. period is due (the return due next, the default), open (the period today is in) or a key from periods. Needs the VAT reports permission. Do not use it for the figures laid out by VAT 201 box (get_vat_return_boxes) or for general VAT rules (explain_vat_return_boxes, check_vat_on_supply).

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

Input Schema

NameRequiredDescriptionDefault
periodNodue (default), open, or YYYY-MM-DD..YYYY-MM-DD from periods.
business_idNoFrom list_businesses. May be left out when the connection shares exactly one business.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.8/5.0
Behavior5/5

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

Beyond the readOnly/idempotent annotations, it discloses the required VAT reports permission, clarifies the data is the user's own records rather than a filed return, and notes the output includes the filing deadline and filed flag. These are behavioral facts annotations cannot express.

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?

Usage guidance is front-loaded, the returned-figures inventory follows, and the exclusions close it out — no filler. It is dense to the point of being one long block, which costs a little readability.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/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 compensates by enumerating the returned fields (output VAT, credit notes, input VAT, reverse charge, net VAT, counts, breakdowns, deadline, filed status). Permission requirements, default behavior, and exclusions are all covered for a moderately complex read tool.

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 the baseline is 3, but the description expands the meaning of 'due' ('the return due next, the default') and 'open' ('the period today is in') beyond the schema's terse equivalents. business_id is left to the schema's list_businesses reference.

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 names a specific verb and resource ('VAT figures for one VAT period of the business') and immediately distinguishes itself from get_vat_return_boxes and the explain/check VAT tools. An agent can tell exactly what this returns without opening the schema.

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

Usage Guidelines5/5

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

It states the triggering user questions ('how much VAT they owe or can reclaim', 'figures for their next VAT return') and explicitly excludes the box-level and rules-based siblings by name, so selection versus alternatives is unambiguous.

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