Skip to main content
Glama

FactorRoute: invoice factoring rules, math and rates

Prime, SOFR and fed funds today

get_benchmark_rates
Read-onlyIdempotent

Today's bank prime loan rate (Federal Reserve H.15), SOFR and 30-day average SOFR (New York Fed) and the fed funds target range, with as-of dates and sources. These price prime-plus factoring and asset-based lines; most flat factoring fees do not move with them.

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": "get_benchmark_rates"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and openWorldHint=false, so the safety profile is covered. The description adds genuine value beyond that: it discloses the upstream sources and that values carry as-of dates, which tells the agent how fresh and how authoritative the numbers are.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two sentences, front-loaded with the payload, followed by a single economic-context sentence that earns its place by telling the agent where these rates apply. No filler, no restating of the title.

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?

For a zero-parameter, read-only fetch with no output schema, the description fully enumerates the returned quantities plus their provenance and dating. An agent has everything needed to decide to call it and to interpret the result.

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 there is nothing for the description to disambiguate. Baseline 4 applies, and the description correctly makes no attempt to invent parameter semantics.

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?

States exactly what is fetched: bank prime (Fed H.15), SOFR, 30-day average SOFR (NY Fed), and the fed funds target range. The description names the specific data sources and the as-of dates/sources included in the response, so an agent knows the precise contents without opening a schema (there are no parameters).

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 second sentence gives clear domain context for when these values matter: they price prime-plus and asset-based factoring lines, while flat factoring fees do not track them. It does not name alternate tools or explicit exclusions, but the applicability condition is concrete and unambiguous.

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