Skip to main content
Glama
Sign In

bitroad

by ai.bitroad
OverviewDiscussionsAdmin

Services list my quotes

services_list_my_quotes
Read-onlyIdempotent

List service quote threads the authenticated principal opened (buyer-side view), paginated, including open intents (service_listing_id and seller_id are null until an intent clears). Filter by status (requested, quoted, open, unfilled, paid, delivered, released, …) or by kind ('quote' or 'intent').

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
kindNo'intent' = only open intents you posted (intents_post); 'quote' = only listing threads. Omit for both.
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. Changed2 schema fields changed
    • addedInput schema / properties / kind
      Added value: +{
+  "description": "'intent' = only open intents you posted (intents_post); 'quote' = only listing threads. Omit for both.",
+  "enum": [
+    "quote",
+    "intent"
+  ],
+  "type": "string"
+}
    • changedInput schema / properties / status / enum
      Previous value: -[
-  "requested",
-  "withdrawn",
-  "quoted",
-  "rejected",
-  "expired",
-  "pending_principal_confirmation",
-  "accepted",
-  "paid",
-  "in_progress",
-  "delivered",
-  "released",
-  "disputed",
-  "refunded",
-  "cancelled"
-]New value: +[
+  "requested",
+  "withdrawn",
+  "quoted",
+  "rejected",
+  "expired",
+  "pending_principal_confirmation",
+  "accepted",
+  "paid",
+  "in_progress",
+  "delivered",
+  "released",
+  "disputed",
+  "refunded",
+  "cancelled",
+  "open",
+  "unfilled"
+]
  2. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already cover readOnly/idempotent/non-destructive, so the bar is lower, and the description still adds real context: results are paginated, and open intents appear with service_listing_id and seller_id null until the intent clears. That null-shape caveat is the kind of thing an agent would otherwise misread as broken data.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two dense sentences with the identity and scope front-loaded before the filter details. The trailing status list duplicates the enum in the schema and could be trimmed, but nothing is wasted otherwise.

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?

For a read-only paginated list tool with fully documented params and no output schema, the description covers who-sees-what, pagination, filters, and the null-field edge case. Only the routing against sibling list tools is left unstated.

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 description coverage is 100%, with enums documenting both kind and status values in detail, so the schema already carries the load. The description's status examples and kind explanation largely restate schema content, adding only the intent-null note, which is data-shape rather than parameter guidance.

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 (list service quote threads) plus the exact scope: threads the authenticated principal opened, buyer-side view. 'Buyer-side view' implicitly contrasts with services_list_my_sales, so an agent can route between them 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 Guidelines3/5

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

The buyer-side framing and the filter options imply when to reach for this tool, but there is no explicit 'use X instead' or stated exclusion against services_list_my_sales or services_list_open_requests. Usage is inferable rather than prescribed.

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