Skip to main content
Glama

FactorRoute: invoice factoring rules, math and rates

Factoring glossary

define_factoring_term
Read-onlyIdempotent

Plain-English definition of an invoice factoring, AR finance, MCA, SBA, UCC, construction or government contracting term (advance rate, recourse, notification, reserve, UCC-1, assignment of claims, retainage, intercreditor...).

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": {
      "term": "<term>"
    },
    "name": "define_factoring_term"
  }
}

Input Schema

NameRequiredDescriptionDefault
termYesThe term to define.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare a safe, read-only, idempotent, closed-world lookup, so the safety profile is covered. The description adds the domain breadth and that output is 'plain-English' rather than citation-heavy, but says nothing about behavior for unknown or ambiguous terms or the shape of the response. Some value, but modest given annotation coverage.

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?

A single front-loaded sentence states the action, output style, and domain scope with no filler. The parenthetical term list is long and dense but earns its place by defining input vocabulary and scope.

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 one-parameter, read-only lookup with no output schema, the description supplies what an agent needs: what is defined, the output style, and the subject-matter boundaries. Only the handling of unrecognized or ambiguous terms is undisclosed, a minor gap for this complexity level.

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?

Schema coverage is 100%, so 'The term to define' is already documented, giving a baseline of 3. The description goes beyond that by enumerating example terms (advance rate, recourse, notification, reserve, UCC-1, assignment of claims, retainage, intercreditor), which communicates the accepted vocabulary and granularity of input.

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?

Names a specific verb ('definition') and a specific resource (a factoring/AR finance/MCA/SBA/UCC/construction/government contracting term), plus concrete examples. An agent can immediately tell this is a glossary lookup, distinct from siblings like get_state_factoring_rules or estimate_factoring_cost, without opening any schema.

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 by the phrase 'plain-English definition' — call it when you need terminology explained — but there is no explicit when-to-use, no exclusions, and no referral to sibling tools for related questions such as state rules or cost calculations. Adequate but leaves routing to inference.

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