Supplier Payment Decision Agent (Ireland)

verify_supplier_payment

Use for supplier identity and VAT reconciliation, not the full signed five-gate invoice decision. Reconciles the claimed legal name, company registration number and VAT number against the Irish Companies Registration Office (IE) and the EU VIES VAT service, and returns an advisory RELEASE, REVIEW, BLOCK or INSUFFICIENT_EVIDENCE decision with per-check results and reason codes plus verification_id. Use decide_supplier_payment for the signed invoice/PO/GRN workflow, individual check tools for one check, and get_verification only to retrieve this stored result. This creates a verification and may call external sources; it never executes or authorises a bank payment. Requires explicit x402 service-fee approval or an authorized bearer token; do not automatically retry paid calls.

Input Schema

Name	Required	Description
`callback`	No
`evidence`	No
`metadata`	No
`supplier`	Yes	Claimed supplier identity and Irish identifiers to reconcile with CRO/VIES; not the signed invoice-decision supplier object.
`policy_id`	Yes	Verification policy identifier; always eu-b2b-payment-v1.
`request_id`	Yes	Caller-generated unique request UUID used for idempotency. This is not the returned verification_id used for retrieval.
`transaction`	No
`requested_at`	No
`schema_version`	Yes	Request schema version; always the literal string 1.0.
`customer_assertions`	No
`payment_destination`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed8 schema fields changedOct 29, 2026

addedInput schema / $defs / SupplierInput / properties / claimed_legal_name / description

Added value: +"Legal supplier name claimed on the invoice, to reconcile with registry evidence."

addedInput schema / $defs / SupplierInput / properties / company_registration_number / description
```
Added value: +"Irish CRO company number, supplied as a string; not a VAT number."
```

addedInput schema / $defs / SupplierInput / properties / country_code / description

Added value: +"Uppercase ISO country code. Company-registry verification currently supports IE only."

addedInput schema / $defs / SupplierInput / properties / vat_number / description

Added value: +"Claimed supplier VAT identifier for VIES reconciliation. Irish VAT validation is supported."

addedInput schema / properties / policy_id / description

Added value: +"Verification policy identifier; always eu-b2b-payment-v1."

addedInput schema / properties / request_id / description

Added value: +"Caller-generated unique request UUID used for idempotency. This is not the returned verification_id used for retrieval."

addedInput schema / properties / schema_version / description

Added value: +"Request schema version; always the literal string 1.0."

addedInput schema / properties / supplier / description

Added value: +"Claimed supplier identity and Irish identifiers to reconcile with CRO/VIES; not the signed invoice-decision supplier object."

Changed8 schema fields changedOct 26, 2026

removedInput schema / $defs / SupplierInput / properties / claimed_legal_name / description

Removed value: -"Legal supplier name claimed on the invoice, to reconcile with registry evidence."

removedInput schema / $defs / SupplierInput / properties / company_registration_number / description
```
Removed value: -"Irish CRO company number, supplied as a string; not a VAT number."
```

removedInput schema / $defs / SupplierInput / properties / country_code / description

Removed value: -"Uppercase ISO country code. Company-registry verification currently supports IE only."

removedInput schema / $defs / SupplierInput / properties / vat_number / description

Removed value: -"Claimed supplier VAT identifier for VIES reconciliation. Irish VAT validation is supported."

removedInput schema / properties / policy_id / description

Removed value: -"Verification policy identifier; always eu-b2b-payment-v1."

removedInput schema / properties / request_id / description

Removed value: -"Caller-generated unique request UUID used for idempotency. This is not the returned verification_id used for retrieval."

removedInput schema / properties / schema_version / description

Removed value: -"Request schema version; always the literal string 1.0."

removedInput schema / properties / supplier / description

Removed value: -"Claimed supplier identity and Irish identifiers to reconcile with CRO/VIES; not the signed invoice-decision supplier object."

Changed8 schema fields changedOct 23, 2026

addedInput schema / $defs / SupplierInput / properties / claimed_legal_name / description

Added value: +"Legal supplier name claimed on the invoice, to reconcile with registry evidence."

addedInput schema / $defs / SupplierInput / properties / company_registration_number / description
```
Added value: +"Irish CRO company number, supplied as a string; not a VAT number."
```

addedInput schema / $defs / SupplierInput / properties / country_code / description

Added value: +"Uppercase ISO country code. Company-registry verification currently supports IE only."

addedInput schema / $defs / SupplierInput / properties / vat_number / description

Added value: +"Claimed supplier VAT identifier for VIES reconciliation. Irish VAT validation is supported."

addedInput schema / properties / policy_id / description

Added value: +"Verification policy identifier; always eu-b2b-payment-v1."

addedInput schema / properties / request_id / description

Added value: +"Caller-generated unique request UUID used for idempotency. This is not the returned verification_id used for retrieval."

addedInput schema / properties / schema_version / description

Added value: +"Request schema version; always the literal string 1.0."

addedInput schema / properties / supplier / description

Added value: +"Claimed supplier identity and Irish identifiers to reconcile with CRO/VIES; not the signed invoice-decision supplier object."

Changed8 schema fields changedOct 22, 2026

removedInput schema / $defs / SupplierInput / properties / claimed_legal_name / description

Removed value: -"Legal supplier name claimed on the invoice, to reconcile with registry evidence."

removedInput schema / $defs / SupplierInput / properties / company_registration_number / description
```
Removed value: -"Irish CRO company number, supplied as a string; not a VAT number."
```

removedInput schema / $defs / SupplierInput / properties / country_code / description

Removed value: -"Uppercase ISO country code. Company-registry verification currently supports IE only."

removedInput schema / $defs / SupplierInput / properties / vat_number / description

Removed value: -"Claimed supplier VAT identifier for VIES reconciliation. Irish VAT validation is supported."

removedInput schema / properties / policy_id / description

Removed value: -"Verification policy identifier; always eu-b2b-payment-v1."

removedInput schema / properties / request_id / description

Removed value: -"Caller-generated unique request UUID used for idempotency. This is not the returned verification_id used for retrieval."

removedInput schema / properties / schema_version / description

Removed value: -"Request schema version; always the literal string 1.0."

removedInput schema / properties / supplier / description

Removed value: -"Claimed supplier identity and Irish identifiers to reconcile with CRO/VIES; not the signed invoice-decision supplier object."

Changed8 schema fields changedOct 17, 2026

addedInput schema / $defs / SupplierInput / properties / claimed_legal_name / description

Added value: +"Legal supplier name claimed on the invoice, to reconcile with registry evidence."

addedInput schema / $defs / SupplierInput / properties / company_registration_number / description
```
Added value: +"Irish CRO company number, supplied as a string; not a VAT number."
```

addedInput schema / $defs / SupplierInput / properties / country_code / description

Added value: +"Uppercase ISO country code. Company-registry verification currently supports IE only."

addedInput schema / $defs / SupplierInput / properties / vat_number / description

Added value: +"Claimed supplier VAT identifier for VIES reconciliation. Irish VAT validation is supported."

addedInput schema / properties / policy_id / description

Added value: +"Verification policy identifier; always eu-b2b-payment-v1."

addedInput schema / properties / request_id / description

Added value: +"Caller-generated unique request UUID used for idempotency. This is not the returned verification_id used for retrieval."

addedInput schema / properties / schema_version / description

Added value: +"Request schema version; always the literal string 1.0."

addedInput schema / properties / supplier / description

Added value: +"Claimed supplier identity and Irish identifiers to reconcile with CRO/VIES; not the signed invoice-decision supplier object."

First observedOct 14, 2026

TDQS

A4.5/5.0

Behavior5/5

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

With no annotations, the description carries the full burden and does so richly: it discloses that it creates a verification, may call external sources, never executes or authorises a bank payment, requires x402 service-fee approval or an authorized bearer token, and must not be auto-retried because it is paid. It also describes the advisory decision values and per-check return shape.

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?

Four dense sentences, front-loaded with the primary use case and routing guidance, and each clause earns its place by covering side effects, auth, and retry policy. It is appropriately sized for a complex paid tool, though the run-on construction is slightly heavy.

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, paid, no-annotation tool with no output schema, the description covers the return decision set, side effects, auth, and sibling routing well. The remaining gap is the purpose of the optional transaction/evidence/payment-destination parameters, which the low schema coverage does not fill.

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 only 36%, so the description should compensate, and it partly does by naming the three supplier identity fields being reconciled. However, the majority of the 11 parameters (transaction, evidence, customer_assertions, payment_destination, callback, metadata) are not explained in the description, leaving a meaningful gap.

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 (reconciles), the exact resources (claimed legal name, company registration number, VAT number), and the authoritative sources (Irish CRO and EU VIES). It immediately distinguishes itself from the signed invoice decision, so an agent can tell it apart from decide_supplier_payment without opening a 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?

Explicitly says when to use it ('supplier identity and VAT reconciliation') and when not ('not the full signed five-gate invoice decision'), then names the alternatives: decide_supplier_payment for the signed workflow, the individual check tools for a single check, and get_verification only for retrieval. Nothing is left to inference.

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

All Supplier Payment Decision Agent (Ireland) 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.

Resources

Need Help?