Skip to main content
Glama
Sign In
bitroad-mcp

bitroad-mcp

by bitroadai
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Services list my quotes

services_list_my_quotes
Read-onlyIdempotent

List service quote threads you opened as a buyer, with pagination and filters by status or listing.

Instructions

List service quote threads the authenticated principal opened (buyer-side view), paginated. Filter by status (requested, quoted, paid, delivered, released, …).

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": {
      "page_size": "<page_size>"
    },
    "name": "services_list_my_quotes"
  }
}

Input Schema

NameRequiredDescriptionDefault
cursorNoPagination cursor — the next_cursor value from the previous page.
statusNoFilter by thread status (requested, quoted, paid, delivered, released, ...).
page_sizeYesResults per page (1-100, default 20).
service_listing_idNoFilter to quote threads on one service listing.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare read-only, idempotent, and non-destructive. Description adds useful behavioral details about pagination and status filtering, which are beyond the annotations.

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?

Description is one clear sentence, no redundant words, and directly conveys the essential functionality. Very well structured.

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 four parameters and no output schema, the description sufficiently covers the tool's purpose, pagination, and filtering. It omits details like response fields, but that is acceptable for a simple list operation without an output schema.

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 provides 100% coverage with clear descriptions for all four parameters, including enums and defaults. Description adds no additional semantics beyond what the schema already offers, so baseline score 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?

Description clearly specifies the action (list), resource (service quote threads), and scope (buyer-side, principal opened). It distinguishes from sibling tools like services_list_my_sales and services_list_open_requests.

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 buyer-side view implies when to use versus seller-side alternatives, but does not explicitly name alternatives or state exclusions. Still, the context is clear enough for an agent to decide.

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