Jithox

Review an invoice

review_invoice

Read-only

Check a structured invoice: Peppol fields, totals, EU VIES VAT, fixes and UBL XML. Never sends; unanswered VAT is unknown. No receiver lookup here. If the receiver has a Peppol address, next call check_peppol_ready with this invoice. 8 credits (EUR 0.08) per review the VAT register answered; needs a bearer token.

Input Schema

TableJSON Schema

Name	Required	Description
`note`	No
`lines`	Yes
`dueDate`	No
`payment`	No	Payment instruction carried by the invoice, when it names an IBAN.
`currency`	No	ISO 4217 currency code (uppercase).
`customer`	Yes	Buyer / accounting customer party, including an optional draft e-mail recipient.
`supplier`	Yes	Seller / accounting supplier party, including an optional IBAN for the payment check.
`totalVat`	No	Caller-stated total VAT (BT-110), used by the arithmetic rule checks.
`issueDate`	Yes
`totalWithVat`	No	Caller-stated invoice total including VAT (BT-112), used by the arithmetic rule checks.
`invoiceNumber`	Yes	Human-readable invoice number, e.g. "INV-2026-0001".
`buyerReference`	No	Buyer reference (BT-10), e.g. a PO or cost-centre code.
`orderReference`	No	Purchase order reference (BT-13). Peppol requires this OR a buyer reference.
`totalWithoutVat`	No	Caller-stated invoice total excluding VAT (BT-109), used by the arithmetic rule checks.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`data`	Yes
`kind`	Yes
`billing`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed16 schema fields changedSep 26, 2026

removedInput schema / properties / currency / default
```
Removed value: -"EUR"
```

changedInput schema / properties / customer / description

Previous value: -"Buyer / accounting customer party."New value: +"Buyer / accounting customer party, including an optional draft e-mail recipient."

addedInput schema / properties / customer / properties / email
```
Added value: +{
+  "type": "string"
+}
```

changedInput schema / properties / customer / properties / endpointScheme / description

Previous value: -"Endpoint scheme id (EAS code)."New value: +"Endpoint scheme id (EAS code), e.g. \"0208\" for a Belgian enterprise number or \"0088\" for a GLN."

addedInput schema / properties / lines / items / properties / lineNetAmount

Added value: +{
+  "description": "Caller-stated line total excluding VAT (BT-131), used by the shared Peppol arithmetic rules.",
+  "type": "number"
+}

addedInput schema / properties / lines / items / properties / lineTotal

Added value: +{
+  "description": "Caller-stated line total excluding VAT, compared with quantity × unit price by this review.",
+  "type": "number"
+}

removedInput schema / properties / lines / items / properties / unitCode / default
```
Removed value: -"EA"
```

changedInput schema / properties / lines / items / properties / unitCode / description

Previous value: -"UN/ECE Rec 20 unit code."New value: +"UN/ECE Rec 20 unit code, e.g. \"HUR\"."

removedInput schema / properties / lines / items / properties / vatPercent / default
```
Removed value: -0
```

addedInput schema / properties / payment

Added value: +{
+  "description": "Payment instruction carried by the invoice, when it names an IBAN.",
+  "properties": {
+    "iban": {
+      "description": "IBAN written on the invoice.",
+      "type": "string"
+    }
+  },
+  "type": "object"
+}

changedInput schema / properties / supplier / description

Previous value: -"Seller / accounting supplier party."New value: +"Seller / accounting supplier party, including an optional IBAN for the payment check."

changedInput schema / properties / supplier / properties / endpointScheme / description

Previous value: -"Endpoint scheme id (EAS code)."New value: +"Endpoint scheme id (EAS code), e.g. \"0208\" for a Belgian enterprise number or \"0088\" for a GLN."

addedInput schema / properties / supplier / properties / iban

Added value: +{
+  "description": "IBAN written on the invoice.",
+  "type": "string"
+}

addedInput schema / properties / totalVat

Added value: +{
+  "description": "Caller-stated total VAT (BT-110), used by the arithmetic rule checks.",
+  "type": "number"
+}

addedInput schema / properties / totalWithVat

Added value: +{
+  "description": "Caller-stated invoice total including VAT (BT-112), used by the arithmetic rule checks.",
+  "type": "number"
+}

addedInput schema / properties / totalWithoutVat

Added value: +{
+  "description": "Caller-stated invoice total excluding VAT (BT-109), used by the arithmetic rule checks.",
+  "type": "number"
+}

Changed72 schema fields changedSep 25, 2026
- removedInput schema / $schema
```
Removed value: -"http://json-schema.org/draft-07/schema#"
```
- removedInput schema / properties / buyerReference / maxLength
```
Removed value: -120
```
- removedInput schema / properties / buyerReference / minLength
```
Removed value: -1
```
- changedInput schema / properties / currency / description
```
Previous value: -"ISO 4217 currency code (uppercase). Defaults to EUR."New value: +"ISO 4217 currency code (uppercase)."
```
- removedInput schema / properties / currency / enum
```
Removed value: -[
-  "EUR",
-  "USD",
-  "GBP",
-  "CHF",
-  "DKK",
-  "SEK",
-  "NOK",
-  "PLN",
-  "CZK",
-  "HUF",
-  "RON",
-  "BGN",
-  "ISK",
-  "JPY",
-  "CNY",
-  "INR",
-  "CAD",
-  "AUD",
-  "NZD",
-  "BRL",
-  "MXN",
-  "ZAR",
-  "AED",
-  "SAR",
-  "SGD",
-  "HKD",
-  "KRW",
-  "TRY",
-  "ILS",
-  "KWD",
-  "BHD",
-  "OMR"
-]
```
- removedInput schema / properties / customer / properties / city / description
```
Removed value: -"City / town name."
```
- removedInput schema / properties / customer / properties / city / maxLength
```
Removed value: -100
```
- removedInput schema / properties / customer / properties / city / minLength
```
Removed value: -1
```
- removedInput schema / properties / customer / properties / countryCode / enum
```
Removed value: -[
-  "AT",
-  "BE",
-  "BG",
-  "HR",
-  "CY",
-  "CZ",
-  "DK",
-  "EE",
-  "FI",
-  "FR",
-  "DE",
-  "GR",
-  "HU",
-  "IE",
-  "IT",
-  "LV",
-  "LT",
-  "LU",
-  "MT",
-  "NL",
-  "PL",
-  "PT",
-  "RO",
-  "SK",
-  "SI",
-  "ES",
-  "SE",
-  "IS",
-  "LI",
-  "NO",
-  "GB",
-  "CH",
-  "US",
-  "CA",
-  "MX",
-  "BR",
-  "AU",
-  "NZ",
-  "JP",
-  "CN",
-  "IN",
-  "KR",
-  "SG",
-  "HK",
-  "AE",
-  "SA",
-  "ZA",
-  "TR",
-  "IL",
-  "UA",
-  "RS"
-]
```
- removedInput schema / properties / customer / properties / endpointId / maxLength
```
Removed value: -60
```
- removedInput schema / properties / customer / properties / endpointId / minLength
```
Removed value: -1
```
- changedInput schema / properties / customer / properties / endpointScheme / description
```
Previous value: -"Endpoint scheme id (EAS code). Defaults to \"0088\" (GLN)."New value: +"Endpoint scheme id (EAS code)."
```
- removedInput schema / properties / customer / properties / endpointScheme / minLength
```
Removed value: -1
```
- removedInput schema / properties / customer / properties / name / description
```
Removed value: -"Trading / display name of the party."
```
- removedInput schema / properties / customer / properties / name / maxLength
```
Removed value: -200
```
- removedInput schema / properties / customer / properties / name / minLength
```
Removed value: -1
```
- removedInput schema / properties / customer / properties / postalZone / description
```
Removed value: -"Postal / ZIP code."
```
- removedInput schema / properties / customer / properties / postalZone / minLength
```
Removed value: -1
```
- removedInput schema / properties / customer / properties / registrationName / description
```
Removed value: -"Legal registration name. Defaults to the trading name."
```
- removedInput schema / properties / customer / properties / registrationName / maxLength
```
Removed value: -200
```
- removedInput schema / properties / customer / properties / registrationName / minLength
```
Removed value: -1
```
- removedInput schema / properties / customer / properties / street / description
```
Removed value: -"Street name and number."
```
- removedInput schema / properties / customer / properties / street / maxLength
```
Removed value: -200
```
- removedInput schema / properties / customer / properties / street / minLength
```
Removed value: -1
```
- removedInput schema / properties / customer / properties / vatId / maxLength
```
Removed value: -60
```
- removedInput schema / properties / customer / properties / vatId / minLength
```
Removed value: -1
```
- removedInput schema / properties / dueDate / description
```
Removed value: -"Optional payment due date (YYYY-MM-DD)."
```
- addedInput schema / properties / dueDate / format
```
Added value: +"date"
```
- removedInput schema / properties / dueDate / pattern
```
Removed value: -"^\\d{4}-(0[1-9]|1[0-2])-(0[1-9]|[12]\\d|3[01])$"
```
- removedInput schema / properties / invoiceNumber / maxLength
```
Removed value: -80
```
- removedInput schema / properties / invoiceNumber / minLength
```
Removed value: -1
```
- removedInput schema / properties / issueDate / description
```
Removed value: -"Issue date (YYYY-MM-DD)."
```
- addedInput schema / properties / issueDate / format
```
Added value: +"date"
```
- removedInput schema / properties / issueDate / pattern
```
Removed value: -"^\\d{4}-(0[1-9]|1[0-2])-(0[1-9]|[12]\\d|3[01])$"
```
- removedInput schema / properties / lines / description
```
Removed value: -"Invoice lines. Totals are computed from these."
```
- removedInput schema / properties / lines / items / properties / description / description
```
Removed value: -"Description of the goods or service for this line."
```
- removedInput schema / properties / lines / items / properties / description / maxLength
```
Removed value: -500
```
- removedInput schema / properties / lines / items / properties / description / minLength
```
Removed value: -1
```
- removedInput schema / properties / lines / items / properties / quantity / description
```
Removed value: -"Quantity invoiced for this line."
```
- removedInput schema / properties / lines / items / properties / quantity / maximum
```
Removed value: -1000000
```
- changedInput schema / properties / lines / items / properties / taxCategory / description
```
Previous value: -"Override the derived UNCL5305 VAT category. Omit to derive S (rated) or Z (zero-rated) automatically from vatPercent."New value: +"Override the derived UNCL5305 VAT category."
```
- changedInput schema / properties / lines / items / properties / unitCode / description
```
Previous value: -"UN/ECE Rec 20 unit code. Defaults to \"EA\" (each)."New value: +"UN/ECE Rec 20 unit code."
```
- removedInput schema / properties / lines / items / properties / unitCode / minLength
```
Removed value: -1
```
- removedInput schema / properties / lines / items / properties / unitPrice / maximum
```
Removed value: -100000000
```
- changedInput schema / properties / lines / items / properties / vatPercent / description
```
Previous value: -"VAT rate as a percentage (0–100). Defaults to 0 (zero-rated)."New value: +"VAT rate as a percentage (0–100)."
```
- removedInput schema / properties / note / description
```
Removed value: -"Free-text invoice note."
```
- removedInput schema / properties / note / maxLength
```
Removed value: -1000
```
- removedInput schema / properties / note / minLength
```
Removed value: -1
```
- removedInput schema / properties / orderReference / maxLength
```
Removed value: -120
```
- removedInput schema / properties / orderReference / minLength
```
Removed value: -1
```
- removedInput schema / properties / supplier / properties / city / description
```
Removed value: -"City / town name."
```
- removedInput schema / properties / supplier / properties / city / maxLength
```
Removed value: -100
```
- removedInput schema / properties / supplier / properties / city / minLength
```
Removed value: -1
```
- removedInput schema / properties / supplier / properties / countryCode / enum
```
Removed value: -[
-  "AT",
-  "BE",
-  "BG",
-  "HR",
-  "CY",
-  "CZ",
-  "DK",
-  "EE",
-  "FI",
-  "FR",
-  "DE",
-  "GR",
-  "HU",
-  "IE",
-  "IT",
-  "LV",
-  "LT",
-  "LU",
-  "MT",
-  "NL",
-  "PL",
-  "PT",
-  "RO",
-  "SK",
-  "SI",
-  "ES",
-  "SE",
-  "IS",
-  "LI",
-  "NO",
-  "GB",
-  "CH",
-  "US",
-  "CA",
-  "MX",
-  "BR",
-  "AU",
-  "NZ",
-  "JP",
-  "CN",
-  "IN",
-  "KR",
-  "SG",
-  "HK",
-  "AE",
-  "SA",
-  "ZA",
-  "TR",
-  "IL",
-  "UA",
-  "RS"
-]
```
- removedInput schema / properties / supplier / properties / endpointId / maxLength
```
Removed value: -60
```
- removedInput schema / properties / supplier / properties / endpointId / minLength
```
Removed value: -1
```
- changedInput schema / properties / supplier / properties / endpointScheme / description
```
Previous value: -"Endpoint scheme id (EAS code). Defaults to \"0088\" (GLN)."New value: +"Endpoint scheme id (EAS code)."
```
- removedInput schema / properties / supplier / properties / endpointScheme / minLength
```
Removed value: -1
```
- removedInput schema / properties / supplier / properties / name / description
```
Removed value: -"Trading / display name of the party."
```
- removedInput schema / properties / supplier / properties / name / maxLength
```
Removed value: -200
```
- removedInput schema / properties / supplier / properties / name / minLength
```
Removed value: -1
```
- removedInput schema / properties / supplier / properties / postalZone / description
```
Removed value: -"Postal / ZIP code."
```
- removedInput schema / properties / supplier / properties / postalZone / minLength
```
Removed value: -1
```
- removedInput schema / properties / supplier / properties / registrationName / description
```
Removed value: -"Legal registration name. Defaults to the trading name."
```
- removedInput schema / properties / supplier / properties / registrationName / maxLength
```
Removed value: -200
```
- removedInput schema / properties / supplier / properties / registrationName / minLength
```
Removed value: -1
```
- removedInput schema / properties / supplier / properties / street / description
```
Removed value: -"Street name and number."
```
- removedInput schema / properties / supplier / properties / street / maxLength
```
Removed value: -200
```
- removedInput schema / properties / supplier / properties / street / minLength
```
Removed value: -1
```
- removedInput schema / properties / supplier / properties / vatId / maxLength
```
Removed value: -60
```
- removedInput schema / properties / supplier / properties / vatId / minLength
```
Removed value: -1
```
- changedOutput schema / (root)
```
Previous value: -nullNew value: +{
+  "properties": {
+    "billing": {
+      "type": "object"
+    },
+    "data": {
+      "type": "object"
+    },
+    "kind": {
+      "type": "string"
+    }
+  },
+  "required": [
+    "kind",
+    "data",
+    "billing"
+  ],
+  "type": "object"
+}
```

Changed1 schema field changedSep 23, 2026

addedInput schema / properties / orderReference

Added value: +{
+  "description": "Purchase order reference (BT-13). Peppol requires this OR a buyer reference.",
+  "maxLength": 120,
+  "minLength": 1,
+  "type": "string"
+}

First observedSep 23, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=true. The description adds value beyond them: 'Never sends', that unanswered VAT is reported as unknown, a rate limit/cost ('8 credits (EUR 0.08) per review the VAT register answered') and an auth requirement ('needs a bearer token'). This is meaningful behavioral context, though it stays terse about what a result contains beyond 'fixes and UBL XML'.

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?

Dense and front-loaded: purpose first, then constraints, then routing, then cost/auth. Every clause carries information, though the telegraphic style makes 'fixes' ambiguous and the cost clause is slightly awkwardly worded.

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 complex nested-schema tool with an output schema present, the description covers the essentials an agent needs: side-effect profile, cost model, auth prerequisite, and next-step routing. Only the exact meaning of 'fixes' and the shape of the review verdict are left implicit, which the output schema presumably carries.

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 coverage is 71% with 14 parameters and rich field-level descriptions (BT codes, EAS schemes, unit codes), so the schema carries most of the semantic load. The description only groups them loosely ('Peppol fields, totals, EU VIES VAT'), adding no syntax or mapping detail, which is the expected baseline when the schema does the heavy lifting.

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/review) on a specific resource (structured invoice) and enumerates the checks performed: Peppol fields, totals, EU VIES VAT, fixes and UBL XML. It also carves out the boundary against siblings by noting 'No receiver lookup here', so an agent can distinguish it from lookup_peppol_participant and check_peppol_ready without reading schemas.

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?

Gives explicit when-to-use routing: 'If the receiver has a Peppol address, next call check_peppol_ready with this invoice.' It also states what not to expect ('No receiver lookup here') and the safety posture ('Never sends'), leaving little to inference.

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

All Jithox tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.