Skip to main content
Glama

BRAINIAC Financial Schedule & Credit Calculations

Analyze receivables dilution

fintech_receivables-dilution-analyze

Quantify how credit notes, disputes, returns, rebates, and write-offs reduce face value in a caller-supplied receivables portfolio. Dilution is capped at face value per receivable and reported by currency without FX conversion. Price $0.04 USDC. POST /api/v1/fintech/receivables-dilution-analyze. Unpaid calls return 402 and do not run.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "receivables": "<receivables>",
      "dilutions": "<dilutions>"
    },
    "name": "fintech_receivables-dilution-analyze"
  }
}

Input Schema

NameRequiredDescriptionDefault
dilutionsYes
receivablesYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does well: it discloses the business rule (dilution capped at face value per receivable), the reporting model (grouped by currency, no FX conversion), the cost ($0.04 USDC), and failure behavior (402 halts execution). It omits edge-case handling such as dilutions referencing unknown receivables or what the response looks like, keeping it short of 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.

Conciseness5/5

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

Five tight sentences, front-loaded with what the tool computes, followed by the calculation rules, then commercial and transport details. Nothing is redundant and each sentence adds operative information.

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?

For a nested two-array tool with no annotations and no output schema, the description covers semantics well but leaves the return shape and validation/error behavior (missing receivables, amounts exceeding face value) unstated. An agent could call it but could not fully predict the response.

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 0%, so the description must compensate and it only partly does: it names the dilution categories matching the schema enum and explains face value and currency grouping. It says nothing about id fields, amount units, the 'detail' field, or the 5,000/20,000 item caps, leaving most parameter meaning to the raw schema.

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?

States a specific verb ('Quantify') and resource ('receivables dilution'), then enumerates the exact dilution kinds covered (credit notes, disputes, returns, rebates, write-offs). This is clearly distinct from the sibling covenant-headroom, repayment-waterfall, and schedule-risk tools, none of which deal with dilution of face value.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies usage ('caller-supplied receivables portfolio') and gives call preconditions (price, 402 on unpaid calls), but never says when to reach for this tool instead of a sibling or what inputs are appropriate. No explicit when-not guidance.

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