Skip to main content
Glama
Sign In

bitroad

by ai.bitroad
OverviewDiscussionsAdmin

Services get quote

services_get_quote
Read-onlyIdempotent

Fetch one service quote thread with its deliverables. Buyer or seller side. Secret deliverables are decrypted only for the buyer; everyone else sees a redaction. Also returns the buyer's own open intents: status 'open' or 'unfilled', null service_listing_id and seller_id, plus category, capability_class, budget_ceiling_pence, deadline_at, bid_window_closes_at and unfilled_reason.

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_get_quote"
  }
}

Input Schema

NameRequiredDescriptionDefault
service_quote_idYesUUID of the quote thread to fetch.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already establish read-only and idempotent behavior, so the description adds real value by disclosing the access-dependent redaction rule: secret deliverables are decrypted only for the buyer and redacted for everyone else. It also explains the unexpected extra payload (the buyer's own open intents), which an agent would otherwise misread. It stops short of covering not-found/unauthorized behavior.

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?

Purpose and access scoping come first, then the redaction rule, then the secondary payload. The trailing field enumeration is long but each field name is load-bearing for an agent that must parse the response. Slightly dense, but no sentence is padding.

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 no output schema, the description carries the return-value burden and does enumerate the open-intent fields in detail, including the distinguishing nulls. It is less complete about the quote thread's own fields and deliverables structure, leaving a modest asymmetry an agent will discover only at call time.

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 coverage is 100% and the single UUID parameter is fully documented in the schema, so the baseline 3 applies. The description adds no format, sourcing, or lookup guidance for service_quote_id beyond what the schema already states.

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?

Opens with a specific verb and resource: 'Fetch one service quote thread with its deliverables.' The singular 'one' contrasts implicitly with the sibling list tool services_list_my_quotes, and the scope ('Buyer or seller side') is stated up front.

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 description implies usage — retrieve a single quote thread by id, viewing it as either party — but never names an alternative or a condition for choosing this over services_list_my_quotes or services_list_my_sales. Nothing is misleading, but the routing guidance is left to inference from the plural/singular naming convention.

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