PabandiOS

pabandi_a2a_negotiate

Autonomous Agent-to-Agent (A2A) booking negotiation. Connects with Pabandi AI Concierge to propose a reservation, verify trust score, calculate dynamic escrow terms, and trigger merchant A2H approval when necessary. Returns proposalId, status, and escrow parameters.

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": {
      "agentId": "<agentId>",
      "businessId": "<businessId>",
      "customerName": "<customerName>",
      "reservationDate": "<reservationDate>",
      "reservationTime": "<reservationTime>",
      "numberOfGuests": "<numberOfGuests>"
    },
    "name": "pabandi_a2a_negotiate"
  }
}

Input Schema

Name	Required	Description
`agentId`	Yes	Unique ID of caller agent
`businessId`	Yes	Target venue ID
`customerName`	Yes	Customer or guest name
`customerPhone`	No	Optional customer contact
`numberOfGuests`	Yes	Party size
`reservationDate`	Yes	Date in YYYY-MM-DD
`reservationTime`	Yes	Time in HH:mm
`specialRequests`	No	Special requirements or notes
`escrowDepositUsdc`	No	Offered escrow deposit amount in USDC
`webhookCallbackUrl`	No	Webhook endpoint to receive async resolution alert

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 4, 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 behavioral burden. It usefully discloses a multi-step workflow and the returned proposalId/status/escrow parameters, but it does not explain permissions, side effects, reversibility, asynchronous approval handling, or what happens if merchant approval is denied.

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?

The description is front-loaded and appropriately sized, with three concise sentences that move from purpose to workflow to return values. The first sentence is a fragment and the Concierge reference is slightly redundant, but there is little wasted 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 complex ten-parameter orchestration tool with no output schema and no annotations, the description gives a useful overview and names key return fields. It still leaves important lifecycle details unclear, including async webhook resolution, proposal expiry, and approval failure behavior.

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 ten parameters. The description adds only high-level context such as trust verification and dynamic escrow terms, without clarifying field relationships or webhook behavior beyond the schema.

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 states a specific resource and workflow: autonomous agent-to-agent booking negotiation, including reservation proposal, trust verification, escrow calculation, and merchant approval. It is clearly more than a generic negotiate tool, but it does not explicitly distinguish itself from sibling booking and escrow tools.

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 phrase 'Autonomous Agent-to-Agent (A2A) booking negotiation' implies when the tool applies, and the approval clause gives some context. However, there is no explicit guidance on when to use this instead of pabandi_create_booking, pabandi_book_stay, pabandi_a2a_get_proposal, or the escrow tools.

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.