Skip to main content
Glama
cmendezs

mcp-einvoicing-de

by cmendezs
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Remote

Tax Rules

tax_rules

Retrieve German VAT rules for e-invoicing: rates, category codes, reverse charge, exemptions, VATEX codes. Use to validate VAT treatment or build invoice logic.

Instructions

Query German VAT rules for e-invoicing.

Returns structured information about VAT rates (19%, 7%), VAT category codes, reverse charge rules under §13b UStG, zero-rate and exemption provisions (§4 UStG), intra-community supply rules, and VATEX exemption reason codes. For use when building invoice creation logic or validating VAT treatment.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
queryYesWhat to look up. Examples: 'reverse_charge', 'rates', 'exemptions', 'kleinunternehmer', '13b', 'zero_rate', 'vatex_codes', or a free-text question about German VAT.
contextNoOptional context about the transaction, e.g. 'construction services' or 'intra-community supply'. Used to filter relevant rules.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed7 schema fields changedv0.11.0
    • addedInput schema / additionalProperties
      Added value: +false
    • addedInput schema / properties / context / anyOf
      Added value: +[
+  {
+    "type": "string"
+  },
+  {
+    "type": "null"
+  }
+]
    • addedInput schema / properties / context / default
      Added value: +null
    • changedInput schema / properties / context / description
      Previous value: -"Optional transaction context to filter results."New value: +"Optional context about the transaction, e.g. 'construction\nservices' or 'intra-community supply'. Used to filter relevant\nrules."
    • removedInput schema / properties / context / type
      Removed value: -"string"
    • changedInput schema / properties / query / description
      Previous value: -"What to look up: 'rates', 'reverse_charge', 'exemptions', 'vatex_codes', etc."New value: +"What to look up. Examples: 'reverse_charge', 'rates',\n'exemptions', 'kleinunternehmer', '13b', 'zero_rate',\n'vatex_codes', or a free-text question about German VAT."
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "additionalProperties": true,
+  "type": "object"
+}
  2. First observedv0.1.0

TDQS

A4/5.0
Behavior4/5

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

No annotations are provided, so the description carries the full burden. It clearly signals a read-only lookup by starting with 'Query' and saying it 'Returns structured information.' It does not discuss rate limits or permissions, but that is acceptable for a simple query tool.

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?

The description is front-loaded with the core action, followed by a dense but relevant enumeration of covered VAT topics, and closes with concrete use cases. Every sentence earns its place, and there is no filler or repetition of schema details.

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?

With an output schema present and both parameters fully documented, the description covers the domain, content, and primary use case well. The only meaningful gap is that it does not route agents away from this tool toward the many sibling code-list tools when a simple code-list lookup is required.

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 baseline is 3. The description does not add meaning beyond the schema for the 'query' and 'context' parameters, though its list of VAT topics hints at valid query intents. It does not explain how context filters the returned rules.

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

Purpose4/5

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

The description uses a specific verb ('Query') and resource ('German VAT rules for e-invoicing'), and enumerates the exact rule categories and statutes covered. It is clear, but it does not explicitly differentiate itself from sibling code-list tools like list_vat_category_codes or check_vatex_code, which overlap on VAT category and VATEX code topics.

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?

It gives explicit context for when to use the tool: 'For use when building invoice creation logic or validating VAT treatment.' However, it does not mention alternatives or exclusion criteria, particularly when an agent should prefer the sibling list/check code-list tools instead.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools