Skip to main content
Glama

FactorRoute: invoice factoring rules, math and rates

State factoring rules

get_state_factoring_rules
Read-onlyIdempotent

Everything FactorRoute has verified about invoice factoring in one US state or DC: commercial financing disclosure law (status, threshold, citation, whether it covers factoring, APR, registration), where UCC liens are filed and searched, how fast state agencies must pay vendors and the late-payment interest, private construction prompt pay, mechanics lien and payment bond deadlines, the main industries and payers, and sources. Use for "is factoring regulated in X", "where do I search UCC liens in X", "how long does X state take to pay contractors".

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": {
      "state": "<state>"
    },
    "name": "get_state_factoring_rules"
  }
}

Input Schema

NameRequiredDescriptionDefault
stateYesState name or two-letter code, e.g. "TX" or "New York". DC is accepted.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/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 fully covered. The description adds genuinely useful context beyond that: it discloses the scope limit of exactly one state per call and details the categories of verified content the agent will receive, which helps it judge whether the result set will answer the question.

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 content is front-loaded — the scope statement comes first, then the data inventory, then usage examples. The middle sentence is a long comma-separated run-on that is dense but still scannable, and nearly every clause names a distinct data domain rather than padding.

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

Completeness5/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 carries the full burden of describing return content, and it does so exhaustively: it enumerates the law status fields, lien filing and search locations, payment deadlines and interest, construction prompt-pay and lien/bond deadlines, industry and payer data, and sources. Combined with annotations covering safety and a fully documented single parameter, an agent has everything needed to call this correctly.

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?

Only one parameter exists and schema coverage is 100%, with the schema itself documenting accepted formats ("TX" or "New York") and DC support. The description echoes the single-state scope ("one US state or DC") but adds no format, casing, or edge-case detail beyond the schema, so the baseline of 3 applies.

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 opens with a specific verb-and-resource framing ("Everything FactorRoute has verified about invoice factoring in one US state or DC") and then enumerates the exact data domains returned — disclosure law status, UCC lien filing locations, prompt-pay deadlines, lien and bond deadlines, industries, and sources. That breadth implicitly distinguishes it from narrower siblings like check_disclosure_requirement or prompt_payment_interest, but no sibling is named, so an agent must infer the distinction.

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?

Three concrete example queries ("is factoring regulated in X", "where do I search UCC liens in X", "how long does X state take to pay contractors") make the intended trigger conditions clear. However, there is no explicit when-not guidance and no routing to the overlapping siblings such as check_disclosure_requirement or list_disclosure_law_states, so an agent may not know which tool to prefer for a single-fact question.

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