Skip to main content
Glama
Sign In
bitroad-mcp

bitroad-mcp

by bitroadai
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Services withdraw quote

services_withdraw_quote
Destructive

Withdraw a pending quote request as a buyer before the seller responds, canceling the request and freeing associated resources.

Instructions

Withdraw a quote request before the seller has quoted (buyer-only).

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": "services_withdraw_quote"
  }
}

Input Schema

NameRequiredDescriptionDefault
service_quote_idYesUUID of the quote request to withdraw.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4.3/5.0
Behavior4/5

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

Adds behavioral constraints (role and timing) beyond the annotations. The destructive nature is consistent with destructiveHint=true, though side effects (e.g., whether the request is deleted or marked withdrawn) are not detailed.

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?

One concise sentence with no redundant words. The structure is clean and directly communicates the action.

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 there is no output schema, the description covers purpose, condition, and role completely. No missing information for a simple withdrawal action.

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 input schema already fully describes the parameter with format, required flag, and a clear description. The tool description adds no extra parameter meaning, so baseline 3 is appropriate.

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 ('withdraw'), resource ('quote request'), and clarifies role ('buyer-only') and condition ('before the seller has quoted'). Clearly distinguishes from sibling actions like accept, reject, or counter.

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?

Provides a temporal condition ('before the seller has quoted') and role restriction ('buyer-only'), which helps the agent decide when to use this tool. Does not explicitly name alternatives, but the context is clear.

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