Skip to main content
Glama

FactorRoute: invoice factoring rules, math and rates

Search FactorRoute guides

search_factoring_guides
Read-onlyIdempotent

Find FactorRoute's guides, situation pages, industry pages, state pages and tools for a question (e.g. "line of credit called", "factor buyout", "staffing payroll", "tax lien", "government contractor"), with each page's short answer and URL.

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": {
      "query": "<query>"
    },
    "name": "search_factoring_guides"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoDefault 5.
queryYesWhat the user wants to know.

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 declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile needs no restating. The description adds value beyond them by disclosing the return shape — each page's short answer and URL — which tells the agent to expect answer text rather than raw document bodies. It does not say how many results come back when limit is unset at the call site, but the schema covers the default.

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 sentence front-loads the verb and the resource before the examples, and nothing is redundant. The five-item example list is somewhat bulky but is the highest-value content in the definition, so it earns its length.

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 only two parameters, no output schema and fully annotated read semantics, the description supplies what is needed: what is searched, what comes back, and how to phrase a query. The only gap is the missing routing signal to sibling tools, which matters given nine closely related alternatives.

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 both parameters are documented structurally and the baseline would be 3. The description earns the extra point by supplying concrete example query strings, which teach the agent how to phrase the free-text query parameter — guidance the schema's "What the user wants to know" does not convey.

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 ("Find") and enumerates exactly what is searched — guides, situation pages, industry pages, state pages and tools — plus concrete example queries. It implicitly positions itself as the broad discovery entry point against narrower siblings like define_factoring_term and get_state_factoring_rules, but never names one, so it falls short of full sibling differentiation.

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 framed as "for a question," and the parenthetical examples ("line of credit called", "factor buyout", "staffing payroll") make the intended input shape clear. However, there is no explicit when-not guidance and no routing statement telling the agent to prefer define_factoring_term for a single definition or get_state_factoring_rules for a specific state, so the agent must infer the split.

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