Skip to main content
Glama
Sign In

bitroad

by ai.bitroad
OverviewDiscussionsAdmin

Factoring sell

factoring_sell
Idempotent

Seller side: sell one delivered job's pending credit to the house at the factoring_quote price. paid_pence is transferred to your Connect account on the next worker run; the job's release then pays the house, and the house bears a refund. One sale per job: a repeat returns it. Refused with factoring_not_eligible, or factoring_ceiling_reached past the per-seller or the house's outstanding limit.

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_sell"
  }
}

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.3/5.0
Behavior5/5

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

Annotations only declare it is a non-read-only, idempotent, non-destructive write; the description goes well beyond that. It explains the money flow (paid_pence to the Connect account on the next worker run, the job's release repays the house, the house bears a refund), the refusal error codes, and the per-seller/house ceiling — exactly the behavioral context an agent needs for a financially consequential call.

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?

Front-loaded with the actor and action, and every sentence carries distinct information. The second sentence is dense — three financial behaviors packed into one semicolon chain — which slightly hurts scanability, but nothing is filler.

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 no output schema, the description compensates well: it covers money movement, timing ('next worker run'), idempotency, and refusal codes. It does not say what the call returns (sale record, net versus paid_pence, any fee or discount at the factoring price), leaving the payout amount slightly ambiguous.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/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 that it must identify a delivered job with pending credit, so the schema carries the load. The description reinforces the 'one delivered job' constraint but adds no new syntax or selection criteria beyond it.

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 ('sell one delivered job's pending credit to the house') plus the pricing reference (factoring_quote) and the actor ('Seller side'). An agent can distinguish this from factoring_quote, which only prices the sale, without opening either 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 prerequisites implicitly via 'delivered job' and the factoring_quote price reference, plus explicit failure conditions ('Refused with factoring_not_eligible, or factoring_ceiling_reached'). The 'one sale per job' rule doubles as guidance on repeat invocation. It stops short of explicitly routing to factoring_quote first, so not a 5.

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