IBANforge

Audit Job Status

audit_status

Read-onlyIdempotent

Check whether a creditor-file audit job is paid and get the report download link once payment is confirmed. Pass the job id and the Stripe session id from the checkout success redirect to retrieve the full report immediately.

Instructions

Check the status of a creditor-file audit job created by audit_creditor_file: whether it is paid, and the download link once it is. USE WHEN: following up on a job id after a human may have paid through the Checkout URL, to learn whether the full report is ready. RETURNS: the same free-preview fields as audit_creditor_file, plus paid, paid_at, and download — a GET /v1/audit/report/{job}?session_id=... path, non-null only once paid AND session_id matches the paying session. Pass the session_id from the Checkout URL's success redirect (its session_id= query parameter) so a just-completed payment is confirmed immediately instead of waiting for the webhook. COST: free.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`job`	Yes	The job id returned by audit_creditor_file.
`session_id`	No	The Stripe Checkout session id, from the success redirect (?session_id=...). Confirms payment immediately when the webhook has not landed yet.

Output Schema

TableJSON Schema

Name	Required	Description
`job`	Yes
`lang`	No
`paid`	Yes
`rows`	No
`tier`	No
`price`	No
`paid_at`	No
`preview`	No
`summary`	No
`checkout`	No
`currency`	No
`download`	No	GET path for the .xlsx report. Non-null only when paid and session_id matched.
`retention`	No
`expires_at`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedv1.8.0Sep 26, 2026
- addedOutput schema / properties / price
```
Added value: +{
+  "type": "number"
+}
```
- removedOutput schema / properties / price_chf
```
Removed value: -{
-  "type": "number"
-}
```
Addedv1.5.0Sep 8, 2026

TDQS

A4.5/5.0

Behavior5/5

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

Annotations already declare readOnlyHint, idempotentHint, and non-destructive behavior, and the description adds rich behavior beyond them: the download is non-null only when paid AND `session_id` matches the paying session, and payment confirmation can happen immediately via `session_id`. No contradiction with annotations.

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 purpose, uses labeled sections (USE WHEN, RETURNS, COST), and every sentence earns its place. It includes the return condition and the session_id nuance without fluff.

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?

For a two-parameter read-only status tool with an output schema present, the description covers when to use it, what it returns, the conditional download availability, and the payment-confirmation edge case. No critical behavior an agent needs to invoke it correctly is missing.

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 100%, so the schema already documents both parameters well. The description reinforces that `session_id` comes from the Checkout success redirect and can avoid webhook delay, but this largely mirrors the schema's own parameter descriptions rather than adding substantial new meaning.

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 states a specific verb and resource: 'Check the status of a creditor-file audit job created by audit_creditor_file.' It also defines the core return value ('whether it is paid, and the download link once it is'), which cleanly distinguishes it from the creating sibling tool.

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 an explicit 'USE WHEN' trigger: following up on a `job` id after a human may have paid through the Checkout URL. It also explains when to pass `session_id` to avoid waiting for the webhook. It does not explicitly state when not to use it, but the context is clear enough.

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

Deploy Server