Skip to main content
Glama

AICTIONBOT™ Werkbank

Invoice against contract: is every invoiced price the agreed price? Overbilling per item, items outside the contract, ready credit note request

compare_invoice_to_contract
Read-onlyIdempotent

AICTIONBOT™ invoice against contract by KULIC Advisory (tool 63). Takes the agreed prices from a contract or price list and the items of an invoice and matches them by description, otherwise by item number. Returns every item billed above the agreed price with the overbilled amount (red), items that are not in the contract (yellow), items billed below the agreed price, the invoice total at contract prices, a ready message asking the supplier for a credit note and the next step. Pass two arrays (contract_rows and invoice_rows) or one array rows with a source column (Contract or Invoice; German: Vertrag or Rechnung). Deterministic, no AI, nothing stored. Not legal advice. To compare an invoice with the previous invoice use compare_invoices, to match it with order and goods receipt use match_documents. Needs sign-in: runs with an AICTIONBOT™ Werkbank licence; without a licence one check per connection every 30 days is free (sign in with “Connect without a licence”).

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

Input Schema

NameRequiredDescriptionDefault
rowsNoAlternative to contract_rows and invoice_rows: one list with a source column (Contract or Invoice) plus the columns above.
languageNoLanguage of the answer. Default de.
supplierNoOptional: supplier name for the message.
invoice_rowsNoInvoice items: position, description, quantity, unit_price, optionally total.
contract_rowsNoAgreed prices: position (item number), description, unit_price. German column names work too.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnly/ idempotent/ non-destructive/ closed-world, so the safety profile is covered; the description adds real context beyond them — deterministic with no AI, nothing stored, the colour-coded output categories, the generated credit-note request, and the licensing/auth condition (Werkbank licence, or one free check per connection every 30 days). The only thing missing is failure behaviour on unmatched or ambiguous descriptions, which is why this is a 4 rather than a 5.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The core purpose and alternatives are front-loaded, but the prose is a single dense run-on that carries branding ('AICTIONBOT™', 'KULIC Advisory', 'tool 63'), a disclaimer, and a long licensing clause. Several of these are useful, yet they are undifferentiated from the operational content and make the definition harder to scan than necessary.

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 fully by enumerating every returned element, including the overbilled amount, the off-contract and under-billed categories, the contract-price total, the draft credit-note message, and the next step. For a read-only comparison tool with five fully documented parameters, nothing an agent needs in order to call it or interpret the result is missing.

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 adds genuine meaning: it explains the relationship between the alternative rows array and contract_rows/invoice_rows, that matching is by description first and item number second, and that German column names (Vertrag/Rechnung) are accepted. It does not explain what happens when a row cannot be matched, so it stops short of a 5.

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 — matching contract/price-list unit prices against invoice items by description and then by item number — and states exactly what it returns (overbilled items, off-contract items, under-billed items, invoice total at contract prices, credit-note message). It explicitly separates itself from compare_invoices and match_documents, so an agent can route without opening another 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 gives explicit when-to-use and when-not-to-use guidance: 'To compare an invoice with the previous invoice use compare_invoices, to match it with order and goods receipt use match_documents.' It also spells out the two accepted calling shapes (contract_rows + invoice_rows, or a single rows array with a Contract/Invoice source column, including German equivalents), which removes the main ambiguity about how to invoke it.

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.