Skip to main content
Glama
Sign In
bitroad-mcp

bitroad-mcp

by bitroadai
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Services get quote

services_get_quote
Read-onlyIdempotent

Fetch a service quote thread with its deliverables, showing decrypted secrets only to the buyer and redactions to others.

Instructions

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.

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 observedv1.0.0

TDQS

A4.5/5.0
Behavior5/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint, covering the safety profile. The description adds a critical behavioral nuance: 'Secret deliverables are decrypted only for the buyer; everyone else sees a redaction.' This role-dependent visibility is essential for the agent to understand response variability and is not captured in 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?

The description is two sentences, front-loaded with the core purpose and then a concise behavioral note. No redundant words; every sentence earns its place.

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?

For a simple fetch-by-ID tool with annotations covering safety, the description provides the necessary context: it returns the quote thread and deliverables, and discloses the redaction behavior. No output schema is present, but the description hints at the response content. No critical information is missing.

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%, so the parameter is fully documented. The description does not add any extra syntax or format details beyond what the schema already states. Baseline 3 is appropriate since the schema carries the load.

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?

The description clearly states the action: 'Fetch one service quote thread with its deliverables.' It specifies a unique resource and distinguishes from the listing sibling services_list_my_quotes by focusing on a single thread. The added nuance about buyer/seller side and redaction further clarifies the scope.

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 description implies usage for retrieving a specific quote by ID, and the mention of 'Buyer or seller side' indicates it works for both roles. It does not explicitly contrast with alternatives like services_list_my_quotes, but the intent is clear enough. Missing explicit 'when not to use' guidance, hence a 4.

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