Skip to main content
Glama
Sign In

bitroad

by ai.bitroad
OverviewDiscussionsAdmin

Settlement contest job

settlement_contest_job
DestructiveIdempotent

Contest one job on the buyer's tab before its settlement cycle captures. The job's whole charge comes off the tab, the quote moves to 'refunded' and the seller is told; this is a reversal, not a dispute, and needs no admin. Allowed while the cycle is 'open' or 'closed' and the quote is paid, in_progress, delivered or released. After capture it refuses with contest_window_closed: file a dispute with disputes_file instead.

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>",
      "reason": "<reason>"
    },
    "name": "settlement_contest_job"
  }
}

Input Schema

NameRequiredDescriptionDefault
reasonYesWhy the job is contested; the seller sees it.
service_quote_idYesUUID of the tab job's quote thread.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.7/5.0
Behavior4/5

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

Annotations already declare destructive=true, idempotent=true, and readOnly=false. The description adds real value beyond them: the whole charge is reversed off the tab, the quote moves to 'refunded', the seller is notified, and no admin approval is needed. It stops short of describing the response payload, but the safety and side-effect profile is well covered.

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?

Three tight sentences: action and timing first, then consequences, then eligibility and the fallback path. Every clause carries information an agent needs.

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 two-parameter mutation with no output schema, the description covers action, side effects, preconditions, error behavior, and the alternative tool. Nothing material 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%, so the baseline is 3. The description adds meaning by clarifying that service_quote_id identifies a single tab job and that the reason is surfaced to the seller, which frames both parameters in the reversal context.

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 ('Contest one job on the buyer's tab') plus the timing constraint 'before its settlement cycle captures'. This lets an agent separate it from disputes_file 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 Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicit eligibility conditions (cycle 'open' or 'closed', quote paid/in_progress/delivered/released) and an explicit when-not path routing to disputes_file with the error code contest_window_closed. Nothing is left to inference.

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