Skip to main content
Glama

FactorRoute: invoice factoring rules, math and rates

Does this business fit invoice factoring?

check_factoring_fit
Read-onlyIdempotent

A first-pass fit check, the same logic as FactorRoute's "Do I qualify?" tool: who pays the invoices, industry, monthly invoicing, facility size, days to pay, the situation (bank declined, MCA refinance, switching factors...) and existing liens. Returns the likely funding route (express to $500K, direct to $3MM, network placement $3MM to $25MM, specialty or outside), why, what to expect and the documents to gather.

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": {
      "customers": "<customers>",
      "facility_size": "<facility_size>"
    },
    "name": "check_factoring_fit"
  }
}

Input Schema

NameRequiredDescriptionDefault
stateNoTwo-letter state code.
industryNoOne of: staffing-agencies, government-contractors, construction-subcontractors, manufacturers, wholesale-distribution, aerospace-defense, business-services, marine-services, oilfield-services, textile-apparel, trucking-freight, medical-insurance, other.
customersYes
situationNo
days_to_payNo
encumbrancesNo
facility_sizeYes
monthly_invoicingNo

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 genuinely new behavior: that the result is a routing decision across four tiers (express to $500K, direct to $3MM, network to $25MM, specialty/outside) and that it also returns reasoning and required documents — return-shape detail the annotations cannot convey.

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 core purpose before the input enumeration and the return description. The parenthetical input list is dense but each item is a distinct decision factor, so little is wasted; the FactorRoute branding reference is the only non-essential clause.

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?

With no output schema, the description correctly spends its back half explaining what comes back (route, rationale, expectations, documents), and it covers the major input dimensions for an 8-parameter tool. The gaps are minor: the state parameter is never mentioned and required fields (customers, facility_size) are not flagged as mandatory.

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 only 25% across 8 parameters, so the description must compensate. It does restate seven of the eight inputs in plain language ("who pays the invoices, industry, monthly invoicing, facility size, days to pay, the situation... existing liens"), but omits the state parameter and never explains how any input influences the routing outcome. Enum values are self-describing, which keeps this adequate rather than poor.

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 operation — a first-pass qualification/fit check for invoice factoring — and enumerates exactly what it evaluates (payer type, industry, invoicing volume, facility size, days-to-pay, situation, liens). It also states the output shape (funding route tiers plus rationale and document list), which separates it from sibling tools like estimate_factoring_cost or compare_mca_vs_factoring.

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?

"A first-pass fit check" implies this is the early-stage screening step before cost estimation or MCA comparison, which is useful. However, no explicit when-to-use/when-not-to-use rule or named alternative is given, so the agent must infer the ordering relative to the other sibling tools.

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