Skip to main content
Glama

FactorRoute: invoice factoring rules, math and rates

States with commercial financing disclosure laws

list_disclosure_law_states
Read-onlyIdempotent

Every US state whose commercial financing disclosure law is in effect or enacted, with dollar threshold, effective date, citation, whether it reaches factoring (accounts receivable purchase) transactions, whether an APR is required, and any provider registration. Use for "which states regulate factoring" or "which states require disclosures on business loans and MCAs".

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_disclosure_law_states"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/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 safety is covered. The description adds real behavioral context beyond them: the population is limited to states with laws 'in effect or enacted', and the returned record includes threshold, effective date, citation, factoring reach, APR requirement and provider registration. No pagination or ordering behavior is mentioned, but for a small fixed list that is minor.

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: the first front-loads scope and enumerates returned fields, the second supplies usage triggers. Every clause earns its place, though the first sentence is long and dense enough that it reads as a run-on list.

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 parameters and no output schema, the description carries the return-shape burden itself and does so by listing the fields returned. Combined with annotations covering safety and idempotency, an agent has everything needed to call and interpret this tool.

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?

The tool takes zero parameters, so the baseline is 4 and there is nothing for the description to disambiguate. No misleading parameter-like language is present.

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 uses a precise verb+resource framing ('Every US state whose commercial financing disclosure law is in effect or enacted') and enumerates the attributes returned, so an agent knows exactly what it gets. It stops short of naming the adjacent siblings (get_state_factoring_rules, check_disclosure_requirement), so the boundary is inferred from the example phrasings rather than stated.

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?

The final sentence gives concrete when-to-use triggers ('which states regulate factoring', 'which states require disclosures on business loans and MCAs'), which is clear context. There are no explicit exclusions or named alternatives telling the agent when to prefer check_disclosure_requirement or get_state_factoring_rules instead.

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