Skip to main content
Glama
Sign In

bitroad

by ai.bitroad
OverviewDiscussionsAdmin

Factoring quote

factoring_quote
Read-onlyIdempotent

Seller side: quote what the house would pay now for one of your delivered jobs' pending credit. Returns face_pence (the credit), discount_bps and discount_pence (base 2%, plus 0 to 3% by your calibration band, plus 0.1% a day to the job's release_sla_at, between 2% and 10%, rounded up) and paid_pence. Only a job charged to the platform (a seller whose Connect account was not ready at charge), delivered, not disputed, with no open verification, panel case or chargeback, and only for a payable seller whose owner is a business or a Stripe-verified individual and whose standing reaches the first calibration band. Refused with factoring_not_eligible and a reason otherwise.

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": {
      "service_quote_id": "<service_quote_id>"
    },
    "name": "factoring_quote"
  }
}

Input Schema

NameRequiredDescriptionDefault
service_quote_idYesUUID of your delivered job whose pending credit you would sell.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.6/5.0
Behavior5/5

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

Annotations already declare readOnly/idempotent/non-destructive, and the description goes well beyond them: it discloses the exact discount formula (2% base, 0–3% calibration band, 0.1%/day to release_sla_at, capped 2–10%, rounded up) and the refusal contract ('factoring_not_eligible and a reason'). That is the pricing and failure behavior an agent needs and cannot get from structured fields.

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?

Purpose and return values are front-loaded, and every clause carries real information (formula, eligibility, error). It is a single dense paragraph with deep nesting ('plus 0 to 3% by your calibration band, plus 0.1% a day to the job's release_sla_at, between 2% and 10%, rounded up') that could be split for faster scanning.

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?

No output schema exists, so the description carries the return contract itself, naming face_pence, discount_bps, discount_pence and paid_pence. Combined with the full eligibility list and refusal code, nothing an agent needs to call or interpret this correctly is missing.

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% and the single parameter already documents itself as the UUID of a delivered job whose pending credit is sold. The description reinforces that the job must be delivered and platform-charged, adding eligibility meaning beyond the schema's format constraints, though it adds no new syntax detail.

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 a specific verb and resource ('quote what the house would pay now for one of your delivered jobs' pending credit') and pins the side ('Seller side'), which separates it from the sibling sell/quote family. An agent can tell what this returns without opening the schema.

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?

Gives an unusually explicit eligibility gate: job must be platform-charged, delivered, undisputed, no open verification/panel case/chargeback, seller payable and in the first calibration band. It does not explicitly route to a sibling (e.g. 'use factoring_sell once you accept'), so the when-versus-alternative framing is implied rather than stated.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All bitroad toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources