Skip to main content
Glama
Sign In

PabandiOS

by io.github.jweezy119
OverviewDiscussionsAdmin

pabandi_book_contractor_escrow

Book a high-ticket contractor milestone (e.g., Chicago Roofing, HVAC, or Commercial Security) with dynamic Trust-Band escrow pricing (Band A = $0 waived, Band B = 50% off, Band C = Standard, Band D = 1.25x capped at 50%). Returns reservationId, computed deposit, and Solana USDC escrow URI.

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": {
      "businessId": "<businessId>",
      "serviceValue": "<serviceValue>",
      "date": "<date>",
      "time": "<time>",
      "customerName": "<customerName>"
    },
    "name": "pabandi_book_contractor_escrow"
  }
}

Input Schema

NameRequiredDescriptionDefault
dateYesRequested date in YYYY-MM-DD format
timeYesRequested time in HH:mm format (e.g. "10:00")
businessIdYesBusiness ID or slug (e.g. "matthews-roofing-chicago", "deljo-heating-cooling-chicago", "alert-protective-security-chicago")
serviceNameNoSelected service or escrow milestone package name
customerNameYesCustomer or principal full name
serviceValueYesFull contract or milestone price in USD/USDC (e.g. 9500)
customerEmailNoCustomer email address
customerPhoneNoCustomer phone number
sdJwtPresentationNoOptional SD-JWT presentation proving the principal trust_band for zero/reduced deposit pricing

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.3/5.0
Behavior3/5

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

With no annotations provided, the description carries the full behavioral burden and discloses useful details: the dynamic Trust-Band pricing formula and the returned reservationId, computed deposit, and Solana USDC escrow URI. However, it does not state permissions, whether booking is binding, cancellation behavior, or the side effects of creating an escrow, leaving significant financial/mutation context undisclosed.

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 and is front-loaded with the core action, 'Book a high-ticket contractor milestone'. The parenthetical pricing bands and return fields are relevant, and there is no filler or redundant wording.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a nine-parameter financial booking tool with no annotations and no output schema, the description covers purpose, pricing, and return values reasonably well. It still omits usage routing among siblings, authentication or prerequisites, and side-effect or cancellation details that an agent would need before invoking a booking-and-escrow operation.

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 schema already documents all nine parameters in detail. The description adds context about Trust-Band pricing and the computed deposit, which helps explain the significance of serviceValue and sdJwtPresentation, but it does not add parameter-level semantics beyond what the schema provides.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description uses a specific verb, 'Book', and a clear resource, 'high-ticket contractor milestone', with examples such as Chicago Roofing, HVAC, and Commercial Security. It does not explicitly distinguish this tool from sibling escrow or booking tools like create_escrow, start_escrow, or create_booking, so it falls short of a 5.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

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

The description implies the tool is for high-ticket contractor milestones, but it gives no explicit when-to-use guidance, no when-not-to-use exclusions, and no alternatives. It does not help an agent choose between this and the many sibling escrow or booking tools.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All PabandiOS 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