Skip to main content
Glama

FactorRoute: invoice factoring rules, math and rates

Merchant cash advance vs. factoring

compare_mca_vs_factoring
Read-onlyIdempotent

Estimated APR of a merchant cash advance from its funded amount, factor rate, fees and term, next to the cost of raising the same cash by factoring invoices. Same math as FactorRoute's MCA vs. factoring tool (IRR of the payment schedule, the method state disclosure rules use to estimate APR).

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": {
      "funded": "<funded>",
      "factor_rate": "<factor_rate>",
      "term_months": "<term_months>"
    },
    "name": "compare_mca_vs_factoring"
  }
}

Input Schema

NameRequiredDescriptionDefault
fundedYesMCA amount funded, dollars.
frequencyNoPayment frequency. Default daily.
days_to_payNoHow long your customers take to pay. Default 45.
factor_rateYesFactor rate, e.g. 1.35.
term_monthsYesMonths to pay back.
origination_pctNoFees withheld, percent of funded. Default 0.
factoring_fee_pct_per_30_daysNoFactoring fee to compare. Default 2.5.

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?

Annotations already declare readOnlyHint, idempotentHint, non-destructive and closed-world, so the safety profile is covered. The description adds real value beyond that by disclosing the calculation method (IRR of the payment schedule) and framing the result as an estimate, which tells the agent how much to trust the number. It does not describe the shape of the returned figures (APR only, or a side-by-side breakdown), which keeps 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.

Conciseness4/5

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

Two sentences, front-loaded with the calculation and comparison before the methodology note. The reference to 'FactorRoute's MCA vs. factoring tool' is slightly self-referential padding, but it earns some place by establishing the provenance of the math.

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 seven-parameter calculator with full schema coverage and no output schema, the description covers what is computed, from which inputs, and by what method. What it leaves out is the composition of the result (whether it returns both APRs, a difference, or a recommendation), which the absence of an output schema makes somewhat more important.

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 every one of the seven parameters, including defaults for frequency, days_to_pay, origination_pct and factoring_fee_pct_per_30_days, is already documented. The description restates the main drivers (funded amount, factor rate, fees, term) but adds no syntax, unit, or interaction detail beyond the schema. Baseline 3 applies.

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 names a specific computation (estimated APR of an MCA) and a specific comparison target (cost of raising the same cash by factoring invoices), including the inputs that drive it. The 'A next to B' framing distinguishes it from single-sided siblings such as estimate_factoring_cost or check_factoring_fit without needing to name them.

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 mention of 'the method state disclosure rules use to estimate APR' signals a compliance/disclosure-estimate context. There is no explicit when-to-use, when-not-to-use, or pointer to a sibling for the single-sided case, so the agent must infer routing.

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