Skip to main content
Glama

BRAINIAC Rental Operations

Report a rental handover

rental-operations_handover-report
Read-onlyIdempotent

Combine the supplied readiness items, payment evidence, inventory comparison, document dates, and obligations. The report does not clear funds, give legal advice, or complete a handover. Price $0.12 USDC. POST /api/v1/rental-operations/handover-report. 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_handover-report"
  }
}

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.
dueCountNodueCount. Number.
findingsNofindings. Array.
paymentsNopayments. Array.
checkedAtNocheckedAt. String.
documentsNodocuments. Array.
inventoryNoinventory. Array.
legalAdviceNolegalAdvice. Boolean.
limitationsNolimitations. Array.
obligationsNoobligations. Array.
rentMatchedNorentMatched. Number.
expiredCountNoexpiredCount. Number.
fundsClearedNofundsCleared. Boolean.
jurisdictionNojurisdiction. String.
missingCountNomissingCount. Number.
requirementsNorequirements. Array.
rulesAppliedNorulesApplied. Boolean.
depositMatchedNodepositMatched. Number.
obligationCountNoobligationCount. Number.
tenantContactedNotenantContacted. Boolean.
handoverCompletedNohandoverCompleted. Boolean.
evictionDeterminedNoevictionDetermined. Boolean.
inventoryDifferenceCountNoinventoryDifferenceCount. Number.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so the description's real contributions are the scope disclaimers (no fund clearing, no legal advice, no handover completion) and the payment mechanics: $0.12 USDC, and an unpaid call returns x402 payment terms without executing. Those payment-failure semantics are behavior an agent cannot get from the annotations and are genuinely useful. It does not contradict readOnlyHint.

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?

Front-loaded with the core action and inputs, then scope limits, then price and transport details. Every sentence carries information, though the bare 'POST /api/v1/rental-operations/handover-report' path is low-value to an agent that invokes tools rather than URLs.

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

Completeness5/5

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

For a 14-parameter, all-optional aggregation tool with an output schema, the description covers what it consumes, what it deliberately does not decide, and how payment gating behaves. Nothing an agent needs in order to call it correctly is missing; return shape is covered by the output schema.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3, and the description earns above baseline by mapping semantic intent onto the generic parameter names: 'readiness items' to items, 'payment evidence' to evidence, 'inventory comparison' to inventory, 'document dates' to documents, 'obligations' to obligations. It does not explain the role of the wrapper fields (csv, json, text, file, asOf, jurisdiction, rules, requirements), which the schema describes only structurally.

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 ('Combine') and enumerates the exact input families it merges: readiness items, payment evidence, inventory comparison, document dates and obligations. That lets an agent distinguish it from the single-check siblings, though it never names a sibling or explicitly frames itself as the aggregate counterpart to them.

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 implied rather than stated: an agent can infer this is the consolidated report versus the individual check tools, and the 'does not clear funds, give legal advice, or complete a handover' sentence usefully rules out over-reading the output. There is no explicit 'use this when you want one combined report instead of running the individual checks' instruction.

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