Skip to main content
Glama

FactorRoute: invoice factoring rules, math and rates

Factoring cost and effective annual rate

estimate_factoring_cost
Read-onlyIdempotent

Cost of factoring one invoice (or one month of invoices): cash advanced, fees, rebate, cost as a percent of the invoice and the effective annual rate on the cash actually received, next to a bank line. Same math as FactorRoute's factoring cost calculator. Fee is a flat rate per 30 days billed in blocks of increment_days (30, 15, 10 or 1 for daily proration).

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": {
      "invoice_amount": "<invoice_amount>",
      "fee_pct_per_30_days": "<fee_pct_per_30_days>",
      "days_outstanding": "<days_outstanding>"
    },
    "name": "estimate_factoring_cost"
  }
}

Input Schema

NameRequiredDescriptionDefault
bank_apr_pctNoBank line APR to compare. Default 10.
monthly_feesNoRecurring monthly fees in dollars (service, lockbox). Default 0.
increment_daysNoBilling block in days. Default 30.
invoice_amountYesInvoice face value in dollars.
advance_rate_pctNoAdvance rate, percent. Default 85.
days_outstandingYesDays until the customer pays.
fee_pct_per_30_daysYesDiscount fee, percent per 30 days (e.g. 2.5).

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?

Annotations already establish this is a safe, idempotent, closed-world read, so the description is free to focus elsewhere and does: it discloses the fee algorithm (flat rate per 30 days, billed in blocks of increment_days with daily proration at 1) and enumerates the computed outputs including the bank-line comparison. That algorithmic detail matters because the rounding/proration behavior changes results, and it is not inferable from annotations.

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?

Three sentences, front-loaded with the computation and outputs before the billing-block mechanics. Dense but every sentence contributes; the 'Same math as FactorRoute's factoring cost calculator' clause is the weakest line, serving as a fidelity claim rather than operational information.

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

Completeness4/5

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

For a 7-parameter deterministic calculator with no output schema, the description does the necessary work of enumerating return values and explaining the fee-proration rule. The remaining gap is guidance on when to prefer this over the comparison and benchmark-rate siblings, which an agent would need to route correctly.

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

Parameters4/5

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

Schema coverage is 100%, so the baseline would be 3, but the description adds real meaning: it explains that fee_pct_per_30_days is a flat rate charged per 30 days, that increment_days selects the billing block (30/15/10/1 for daily proration), and that the tool supports monthly aggregation. This goes beyond the schema's one-line parameter hints without contradicting them.

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 description names the exact computation and object: cost of factoring one invoice (or a month of invoices), with a concrete list of outputs (cash advanced, fees, rebate, cost percent, effective annual rate, bank-line comparison). It is clearly a calculator, not a lookup or policy tool, though it never names a sibling to distinguish itself from, leaving that differentiation implicit.

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?

Usage is implied rather than stated: the agent can infer this is the tool for pricing a specific invoice scenario, and the 'one invoice or one month of invoices' phrasing hints at scope. But there is no explicit when-to-use/when-not, no prerequisites, and no routing to alternatives such as compare_mca_vs_factoring or get_benchmark_rates for side-by-side product comparisons.

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