Skip to main content
Glama

YESbusiness

VAT periods

list_vat_periods
Read-onlyIdempotent

The company's VAT periods, oldest first: id (what update_vat_period takes), date_from, date_until (null = open-ended), is_vat_registered, vat_number, method ('effective' or 'net' = net tax rate, TDFN / Saldosteuersatz) and basis ('agreed' = VAT due on invoicing, 'collected' = on payment). Use it to answer whether and since when the company is VAT-registered and which method it uses on a date. A company with no period cannot book with VAT.

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": {
      "company_id": "<company_id>"
    },
    "name": "list_vat_periods"
  }
}

Input Schema

NameRequiredDescriptionDefault
company_idYesThe company to work on — one of list_my_companies' company_id values.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior5/5

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

Annotations already declare read-only, idempotent, non-destructive, closed-world behavior, so the description focuses on domain semantics instead. It discloses result ordering, that date_until null means open-ended, the meaning of both method values (effective/net, TDFN/Saldosteuersatz) and both basis values (agreed/collected), and the downstream consequence of an empty result.

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?

Front-loaded with the resource and ordering, then the use case, then a caveat — a sensible priority order with no filler. The first sentence is long and parenthesis-heavy, which slightly slows scanning, but every clause carries information.

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?

There is no output schema, and the description compensates by enumerating the returned fields and decoding their possible values, including the null case. An agent can call this and interpret the response correctly without further documentation.

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?

Only one parameter and schema coverage is 100%, with the schema itself pointing at list_my_companies for valid ids. The description adds no format, constraint, or sourcing guidance for company_id beyond that, so the baseline applies.

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+resource ("The company's VAT periods") and immediately scopes it with ordering ("oldest first") and a field list. It is clearly separable from siblings like list_vat_codes or get_vat_statement, and it even cross-references update_vat_period as the consumer of the id.

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?

Explicitly names the question this tool answers: whether and since when the company is VAT-registered, and which method applies on a given date. It adds a useful exclusionary fact ("a company with no period cannot book with VAT"), but does not explicitly redirect to list_vat_codes for the per-code dimension.

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