Fusion Holds & Funds Desk MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| LOG_LEVEL | No | debug, info, warn, error, or silent. Logs go to stderr. | info |
| FUSION_MODE | No | Set to 'mock' or 'live'. Defaults to 'mock'. | mock |
| FUSION_TOKEN | No | Bearer token; takes precedence over basic auth. | |
| FUSION_BASE_URL | No | Pod origin. Required in live mode. | |
| FUSION_PASSWORD | No | Basic auth password for the integration user. | |
| FUSION_USERNAME | No | Basic auth username for the integration user. | |
| FUSION_TIMEOUT_MS | No | Per-request timeout in milliseconds. | 30000 |
| FUSION_MAX_RETRIES | No | Retries for 429 and 5xx responses. | 2 |
| FUSION_DEFAULT_LEDGER | No | Ledger used when a call omits ledgerName. | |
| FUSION_BC_BALANCES_ENABLED | No | Opt in to querying Budgetary Control balances. Off means balances are always reported as unavailable. | false |
| FUSION_DEFAULT_BUSINESS_UNIT | No | Business unit used when a call omits businessUnit. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
| logging | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_invoiceA | Retrieve a single Oracle Fusion Payables invoice: header, amounts, validation/approval/payment status, matched purchase orders, and lines. Identify the invoice by invoiceId, or by invoiceNumber plus supplierName/supplierNumber/businessUnit when the number alone is ambiguous. Use this first to establish the facts of an invoice, then call get_invoice_holds, get_accounting_period_status, or get_budgetary_control_impacts for the reason it is stuck. |
| get_invoice_holdsA | List the holds on an Oracle Fusion Payables invoice and explain each one: what the hold code means, which team owns the fix, whether revalidation can release it, and the steps that clear it. Returns prioritised recommended actions and flags whether payment or accounting is blocked. Use after get_invoice when an invoice is not paying or not accounting. |
| get_accounting_period_statusA | Report Oracle Fusion accounting period status for Payables (AP) and General Ledger (GL): Open, Closed, Permanently Closed, Never Opened, or Future Enterable. Query by period name, or by accountingDate to resolve the period that contains an invoice's accounting date. Use this when an invoice will not account, when an accounting date is rejected, or before asking for a period to be reopened. If a period status cannot be read it is reported as unavailable with the reason; a status is never assumed. |
| get_budgetary_control_impactsA | Explain the budgetary control impact on an Oracle Fusion Payables invoice: the funds check / funds reservation status, which control budgets are involved, and which lines and distributions failed and why. Use when an invoice carries an Insufficient Funds or Funds Check Failure hold, or before promising a payment date on a budget-controlled invoice. Important: this tool never estimates or derives funds balances. Budget and funds-available figures are reported only when Oracle Budgetary Control returns them; otherwise they are null with the reason they are unavailable and guidance on where to obtain them. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 4 tools
Each tool addresses a distinct diagnostic question: invoice facts, hold explanations, period status, and budget impacts. The descriptions explicitly reference the recommended sequence, eliminating boundary confusion.
All tool names follow a uniform get_ + noun phrase pattern in snake_case, making the resource and action clear for every tool. The naming convention is perfectly consistent.
Four tools cover a tightly scoped diagnostic domain without redundancy. Each tool earns its place and together they form a complete workflow for investigating stuck invoices.
The set covers the full diagnostic surface for the stated purpose: invoice retrieval, holds analysis, period status, and budgetary control impacts. No obvious missing operation within the read-only holds desk scope.