Skip to main content
Glama

FactorRoute: invoice factoring rules, math and rates

Does this factoring deal need a state disclosure?

check_disclosure_requirement
Read-onlyIdempotent

For a business in a given state and a deal size in dollars, says whether that state's commercial financing disclosure law likely applies to an invoice factoring deal, based on the law's status, threshold and whether it covers accounts receivable purchases. Coverage also depends on exemptions (banks, low-volume providers) and on where the business is located, so treat it as a first check.

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>",
      "amount_usd": "<amount_usd>"
    },
    "name": "check_disclosure_requirement"
  }
}

Input Schema

NameRequiredDescriptionDefault
stateYesState where the business is located (name or code).
amount_usdYesTotal facility or deal amount in US dollars.

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 cover the safety profile (readOnlyHint, idempotent, non-destructive, closed-world), so this is bonus territory. The description still adds real value by disclosing that the answer is probabilistic ("likely"), depends on law status, thresholds, AR-purchase coverage, and exemptions for banks and low-volume providers, and that location matters — material caveats an agent would otherwise miss.

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 question and followed by the limiting factors. The second sentence is dense but every clause (exemptions, location, first-check framing) carries information; minor tightening of the long sentence would help.

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?

With no output schema, the description does describe the shape of the answer (a yes/likely verdict) and its limits, which is adequate. It stops short of stating what the response actually contains, whether confidence or reasoning is returned, or what the agent should do next, leaving a modest gap for a question-answering tool.

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 coverage is 100%, and the schema documents both state (name or code) and amount_usd (total facility or deal amount). The description only restates these inputs in prose and adds no format, range, or edge-case detail beyond the schema, so the baseline 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 names a specific question and resource: whether a state's commercial financing disclosure law applies to an invoice factoring deal, given state and amount. It is clearly scoped as a preliminary screen ("treat it as a first check"), which hints at a more authoritative rules sibling, but no alternative tool is named explicitly.

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?

It sets the context for use (a business in a given state plus a dollar deal size) and positions the tool as a first-pass check rather than a definitive determination. It does not name a follow-up tool such as get_state_factoring_rules or state when not to use it, so exclusions are left implicit.

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