IBANforge

Audit Job Status

audit_status

Read-onlyIdempotent

Check whether a creditor-file audit job is paid and obtain the report download link once payment completes. Pass the job id and session_id to confirm payment immediately after checkout.

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
`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.
`price_chf`	No
`retention`	No
`expires_at`	No

Schema Changelog

Changes observed during successful MCP inspections.

Addedv1.5.0Sep 8, 2026

TDQS

A5/5.0

Behavior5/5

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

Beyond the readOnly and idempotent annotations, the description discloses specific behaviors: the download field is non-null only when paid AND session_id matches, and that session_id bypasses webhook delays. This adds transparency about the tool's internal logic.

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 well-structured with clear sections (USE WHEN, RETURNS) and each sentence serves a purpose. It is informative without being redundant, condensing important details about parameters and conditional behavior into a compact format.

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?

Given the tool has an output schema (not shown) and the description mentions what fields are returned (free-preview fields, paid, paid_at, download), it provides enough context for a caller to understand the response. The description also covers the special session_id handling, making it complete for usage.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The schema descriptions already cover both parameters, but the tool description adds crucial context: job is the id from audit_creditor_file, and session_id is the Stripe Checkout session id from the success redirect, explaining its role in confirming payment immediately.

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 clearly states that the tool 'checks the status of a creditor-file audit job' and explains it returns payment status and download link. It distinguishes from siblings by referencing the job created by audit_creditor_file, making its purpose unique and specific.

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?

The description explicitly says 'USE WHEN' and details the scenario: following up on a job id after a human may have paid through Checkout URL. It also explains when to pass session_id to confirm payment immediately, providing concrete usage guidance.

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

Deploy Server