PabandiOS

pabandi_book_property

Reserve or lease a property unit/stay experience in PropertyOS on behalf of a tenant or guest. Automatically verifies tenant trust risk band via CourtListener, allocates lease deposit into escrow, and issues a cNFT booking pass.

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": {
      "propertyId": "<propertyId>",
      "startDate": "<startDate>",
      "tenantName": "<tenantName>",
      "tenantEmail": "<tenantEmail>"
    },
    "name": "pabandi_book_property"
  }
}

Input Schema

Name	Required	Description
`unitId`	No	Specific unit ID (optional)
`endDate`	No	Lease/Stay end date (YYYY-MM-DD)
`startDate`	Yes	Lease/Stay start date (YYYY-MM-DD)
`propertyId`	Yes	Property ID or unit slug
`tenantName`	Yes	Tenant or guest name
`monthlyRent`	No	Monthly rent or total stay value
`tenantEmail`	Yes	Tenant email for e-signature / lease receipts
`tenantPhone`	No	Tenant phone number
`depositAmount`	No	Security deposit amount

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 9, 2026

TDQS

B3.2/5.0

Behavior3/5

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

With zero annotations the description carries the full burden, and it does disclose real side effects an agent must know about: a CourtListener trust-band check, automatic allocation of the deposit into escrow, and issuance of a cNFT booking pass. It stops short of the operationally critical points: what happens if the trust band is high risk, whether funds are locked before or after verification, and whether the booking can be reversed (a pabandi_cancel_booking sibling exists but is never referenced).

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?

A single front-loaded sentence with no filler; the action leads and the three side effects follow. It is efficient, though the trailing 'stay experience' phrasing adds ambiguity rather than information.

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 money- and identity-touching mutation with no annotations and no output schema, the description gives a useful pipeline summary (verify, escrow, mint) but omits failure modes, permissions, and the fact that no return value is documented anywhere. It is enough to orient an agent but not enough to call safely in edge cases.

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 every one of the 9 parameters is already documented in the input schema. The description adds no parameter meaning, defaults, or format guidance beyond that, which is the expected baseline when the schema does the work.

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?

States a specific verb and resource ('Reserve or lease a property unit/stay experience in PropertyOS on behalf of a tenant or guest') and lists the concrete effects: trust verification, escrow deposit, cNFT pass. The purpose is legible without opening the schema. However, 'stay experience' overlaps directly with sibling pabandi_book_stay (and pabandi_create_booking), and nothing in the description distinguishes this tool from those.

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?

No when-to-use or when-not-to-use guidance. Siblings pabandi_book_stay, pabandi_create_booking, and pabandi_check_availability all compete for the same intent, yet none is named or contrasted. There is also no stated prerequisite such as confirming availability before booking.

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.