Skip to main content
Glama

BRAINIAC Rental Operations

Check move-in readiness

rental-operations_tenant-move-in-readiness
Read-onlyIdempotent

Compare supplied move-in items with the items the caller marks as required. A pending item is not counted as present, and a complete list does not mean the handover was done. Price $0.05 USDC. POST /api/v1/rental-operations/tenant-move-in-readiness. An unpaid call returns the x402 payment terms and does not run.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "rental-operations_tenant-move-in-readiness"
  }
}

Input Schema

NameRequiredDescriptionDefault
csvNocsv, string, length 0 to 200000. Optional.
asOfNoasOf, string, length 0 to 40. Optional.
fileNofile, object. Optional.
jsonNojson, string, length 0 to 200000. Optional.
textNotext, string, length 0 to 200000. Optional.
itemsNoitems, array. Optional.
rulesNorules, array. Optional.
evidenceNoevidence, array. Optional.
expectedNoexpected, array. Optional.
documentsNodocuments, array. Optional.
inventoryNoinventory, array. Optional.
obligationsNoobligations, array. Optional.
jurisdictionNojurisdiction, string, length 0 to 40. Optional.
requirementsNorequirements, array. Optional.

Output Schema

NameRequiredDescriptionDefault
statusNostatus. String.
findingsNofindings. Array.
suppliedNosupplied. Array.
checkedAtNocheckedAt. String.
legalAdviceNolegalAdvice. Boolean.
limitationsNolimitations. Array.
fundsClearedNofundsCleared. Boolean.
requirementsNorequirements. Array.
rulesAppliedNorulesApplied. Boolean.
tenantContactedNotenantContacted. Boolean.
handoverCompletedNohandoverCompleted. Boolean.
evictionDeterminedNoevictionDetermined. Boolean.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, open-world, non-destructive, so the description's real value is the evaluation rules (pending items do not count as present; a complete list does not imply handover was done) plus the paid-call mechanics: $0.05 USDC, the POST endpoint, and the fact that an unpaid call returns x402 payment terms and does not execute. That is substantive behavior beyond the annotations, though it never describes result semantics beyond the rule caveats.

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?

Four short sentences, purpose front-loaded, then rule caveats, then cost and transport details. No filler, though the payment sentence and the endpoint string could be tightened.

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?

Return values need not be explained since an output schema exists, and payment failure behavior is covered. However, for a 14-parameter tool with nested objects and a near-identical sibling, the absence of input-mode guidance (csv vs json vs file vs text) and of any sibling differentiation leaves real gaps.

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% across 14 parameters, so the schema already documents each field's type and bounds. The description only hints that `requirements` holds the caller-marked required items and that `items` holds the supplied ones; it says nothing about asOf, file/csv/json/text input alternatives, or the rules array.

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 comparison target: "Compare supplied move-in items with the items the caller marks as required." That is clear enough to act on, but it never distinguishes itself from the sibling move-in-inventory-compare, which sounds like the same operation.

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?

There is no explicit when-to-use guidance, no prerequisites, and no exclusions or named alternatives. The agent has to infer the trigger from the name and the comparison wording alone, and cannot tell when to prefer this over move-in-inventory-compare.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources