PabandiOS

pabandi_create_quote

Create a dynamic milestone quote with programmable escrow for service businesses & contractors. Break down projects into phases (e.g. 30% deposit, 35% rough-in, 35% signoff) and generate a shareable checkout URL supporting Square, Solana Pay (USDC), and Raast.

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>",
      "title": "<title>",
      "totalAmount": "<totalAmount>"
    },
    "name": "pabandi_create_quote"
  }
}

Input Schema

Name	Required	Description
`title`	Yes	Project title (e.g., "Full Roof Tear-Off & Shingle Replacement")
`businessId`	Yes	Business ID, slug, or serviceBusinessId
`clientName`	No	Client name
`milestones`	No	Optional custom milestone list; auto-generated if omitted
`clientEmail`	No	Client email
`totalAmount`	Yes	Total project quote value in USD/USDC
`depositPercentage`	No	Initial mobilization deposit % (default: 30)

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 9, 2026

TDQS

B3.4/5.0

Behavior3/5

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

With no annotations, the description carries the full burden, and it does disclose two real behavioral facts: the tool generates a shareable checkout URL and that URL supports Square, Solana Pay (USDC), and Raast. It omits auth/permission requirements, whether the quote is persisted or expirable, idempotency, and what happens if milestones conflict with totalAmount.

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 tight sentences, front-loaded with the action and followed by the mechanics. Minor marketing phrasing ('programmable escrow') is offset by the concrete percentage example that earns its space.

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 seven-parameter mutation tool with no annotations and no output schema, the description is adequate but thin: it hints at the returned checkout URL, yet leaves permissions, error conditions, and the milestone-versus-totalAmount invariant unexplained.

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 seven parameters and the baseline is 3. The description only adds a concrete milestone-splitting example that hints at how milestones/depositPercentage relate, without clarifying the interaction (e.g., whether milestone amounts must sum to totalAmount).

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 gives a specific verb and resource ('Create a dynamic milestone quote') plus the distinguishing output ('generate a shareable checkout URL'), which separates it from generic escrow siblings like pabandi_create_escrow or pabandi_finance_quote. It never explicitly names those siblings, so an agent must infer the boundary itself.

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?

Usage is only implied through the audience framing ('service businesses & contractors') and the phase example (30% deposit, 35% rough-in, 35% signoff). There is no explicit when-to-use, when-not-to-use, or 'use X instead' guidance despite many overlapping escrow/quote siblings in the toolset.

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

All PabandiOS tools Inspect

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.