Skip to main content
Glama
Sign In
bitroad-mcp

bitroad-mcp

by bitroadai
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Services purchase

services_purchase

Buy a fixed-price service in a single call: validates scope, computes price, and charges immediately, eliminating seller round-trip.

Instructions

Buy a fixed-price service in one call: validates the scope, computes the deterministic price, creates the quote thread directly in accepted, and charges immediately — no human seller round-trip. Same delegation/envelope enforcement as services_accept_quote.

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_listing_id": "<service_listing_id>",
      "scope": "<scope>",
      "acknowledged_confirmation": "<acknowledged_confirmation>"
    },
    "name": "services_purchase"
  }
}

Input Schema

NameRequiredDescriptionDefault
scopeYesScope-of-work values; must conform to the listing's scope_schema. The metered field drives the computed price.
payment_method_idNoUUID of a saved payment method to charge. Omitted = envelope-bound card, else the principal's default.
requested_summaryNoFree-text description of the work being requested.
confirmation_tokenNoToken from the confirmation_required kickback; must match to complete the charge.
service_listing_idYesUUID of the fixed-price service listing to buy.
__outcomeForTestingNoTest-only: force a simulated card outcome. Never set in production.
acknowledged_confirmationYesSet true when retrying after a confirmation_required kickback, together with confirmation_token.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4.4/5.0
Behavior5/5

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

The description fully discloses the tool's side effects: it 'validates the scope, computes the deterministic price, creates the quote thread directly in accepted, and charges immediately.' It also notes that it operates without human seller interaction. This goes beyond the annotations (which only indicate false readOnly and idempotent) by specifying the actual state-changing operations performed.

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?

The description is two sentences: the first clearly states the main action and internal behavior, and the second provides a useful cross-reference to a sibling tool. It is concise, front-loaded, and free of fluff or redundancy.

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?

Given the tool's moderate complexity (multiple parameters, confirmation flow hinted in the schema), the description covers the primary purpose and high-level behavior well. It does not explicitly mention the confirmation_required kickback flow or that a retry may be needed, but these details are present in the schema and annotations, so the description is reasonably complete.

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?

The schema itself has 100% parameter description coverage, so the tool description does not need to repeat parameter details. However, the tool description adds no parameter-level meaning beyond what is already in the schema. Since coverage is high, the baseline is 3, and there is no additional parameter insight to warrant a higher score.

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?

The description clearly states the tool's purpose: 'Buy a fixed-price service in one call.' It specifies the resource (fixed-price service) and the action (buy), and distinguishes it from quote-based flows by noting 'no human seller round-trip' and 'creates the quote thread directly in accepted.' This makes it immediately obvious when to use this tool versus quote-based alternatives.

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 description gives clear context for when to use the tool: for fixed-price services with immediate purchase and no negotiation. It also references 'Same delegation/envelope enforcement as services_accept_quote' for payment handling. However, it does not explicitly state when not to use it (e.g., when a listing requires manual quote approval), so it lacks an explicit exclusion clause.

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

Deploy Server

Other Tools