Skip to main content
Glama

BRAINIAC Trade Finance & Receivables Intelligence

Detect invoice assignment conflicts

trade-finance_invoice-assignment-conflict-detect
Read-onlyIdempotent

Flag when the same invoice id or number is assigned to more than one assignee in the supplied set. Price $0.04 USDC. POST /api/v1/trade-finance/invoice-assignment-conflict-detect. An unpaid call returns the x402 payment terms and does not run.

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": "trade-finance_invoice-assignment-conflict-detect"
  }
}

Input Schema

NameRequiredDescriptionDefault
csvNocsv, string, length 0 to 200000. Optional.
asOfNoasOf, string, length 0 to 40. Optional.
fileNofile, object. Optional.
jsonNojson, string, length 0 to 200000. Optional.
textNotext, string, length 0 to 200000. Optional.
partiesNoparties, array. Optional.
invoicesNoinvoices, array. Optional.
contractsNocontracts, array. Optional.
documentsNodocuments, array. Optional.
worldBankNoworldBank, object. Optional.
assignmentsNoassignments, array. Optional.
discountRatePctNodiscountRatePct, number, from 0 to 100. Optional.
lettersOfCreditNolettersOfCredit, array. Optional.

Output Schema

NameRequiredDescriptionDefault
itemsNoitems. Array.
statusNostatus. String.
findingsNofindings. Array.
checkedAtNocheckedAt. String.
limitationsNolimitations. Array.
invoiceCountNoinvoiceCount. Number.
conflictCountNoconflictCount. Number.
publicSourcesNopublicSources. Array.
amountInventedNoamountInvented. Boolean.
apiKeyRequiredNoapiKeyRequired. Boolean.
creditDecisionNocreditDecision. Boolean.
paidProviderUsedNopaidProviderUsed. Boolean.
financingApprovedNofinancingApproved. Boolean.
discrepancyInventedNodiscrepancyInvented. Boolean.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Beyond the read-only, idempotent, and non-destructive annotations, the description discloses the exact $0.04 USDC price and the important x402 behavior that an unpaid call returns payment terms without running. The POST route adds invocation context, but external-processing behavior and other operational constraints are not explained.

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?

The description is compact and front-loads the exact detection rule, followed by cost and payment behavior. The raw endpoint sentence is of limited value to an MCP caller and could have been replaced with more actionable input guidance.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The core rule and payment behavior are sufficient to understand the tool, and the output schema removes the need to describe returned conflicts here. However, for a nested 13-parameter schema in which every parameter is optional, the lack of minimum-input and source-precedence guidance leaves significant invocation ambiguity.

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 100%, so the baseline is 3. The description usefully connects invoice id or number with the assignee comparison, but it does not identify a minimum viable payload, explain structured versus csv/json/text/file inputs, or clarify matching and normalization behavior.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The opening sentence gives a precise operation and detection rule: the same invoice id or number appearing under more than one assignee in the supplied set. This is substantially clearer than restating the title, although it does not explicitly contrast the tool with sibling consistency or document checks.

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?

The duplicate-assignment condition establishes a clear use case: checking a supplied set for invoice assignments to multiple assignees. There is no when-not guidance or routing to an alternative for other trade-finance checks, and no advice on selecting an input mode.

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.

Resources