Skip to main content
Glama
Sign In
bitroad-mcp

bitroad-mcp

by bitroadai
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Purchase confirm intent

purchase_confirm_intent

Confirm a purchase intent by re-validating the price, charging via Stripe Connect, and creating the order. Acknowledge confirmation tokens and handle SCA or declined errors.

Instructions

Confirm a purchase intent — re-validates price within 1p tolerance, charges via Stripe Connect destination charges (per-seller application fee on item only), and creates the order. May return SCA / payment-action-required / declined errors.

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": {
      "intent_id": "<intent_id>",
      "acknowledged_confirmation": "<acknowledged_confirmation>"
    },
    "name": "purchase_confirm_intent"
  }
}

Input Schema

NameRequiredDescriptionDefault
intent_idYesUUID of the purchase intent to confirm.
confirmation_tokenNoToken from the confirmation_required response; must match when acknowledging a confirmation.
__outcomeForTestingNoTest-only override of the simulated card outcome. Omit in normal use.
acknowledged_confirmationYesSet true to acknowledge an intent that requires explicit confirmation. Defaults to false.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4.5/5.0
Behavior5/5

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

Discloses important side effects: price re-validation, charging the buyer, creating the order, and possible SCA/declined/provider errors. This goes beyond the annotations, which only mark the tool as non-read-only and non-idempotent.

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?

Single compact sentence covering purpose, key behavior, and error types without redundancy or unnecessary detail.

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?

Given that there is no output schema, the description sufficiently explains what the tool does and what errors may occur. It provides enough context for an agent to invoke it correctly.

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 covers all parameters with descriptions, so the description adds little beyond the schema. The confirmation_token and acknowledged_confirmation fields are already well documented in the schema.

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?

Clearly states the tool confirms a purchase intent, with specific actions: re-validating price, charging via Stripe Connect, and creating the order. This distinguishes it from sibling tools like purchase_create_intent and purchase_cancel_intent.

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?

Describes the confirmation flow and possible error outcomes, making its use context clear. It does not explicitly contrast with alternatives such as purchase_cancel_intent, but the confirmation-focused wording is sufficient for most agents.

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