Skip to main content
Glama

BRAINIAC Rental Operations

Compare move-in inventory

rental-operations_move-in-inventory-compare
Read-onlyIdempotent

Compare a baseline inventory with the move-in list by room, name, condition, and count. A difference is not a finding of liability. Price $0.05 USDC. POST /api/v1/rental-operations/move-in-inventory-compare. 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_move-in-inventory-compare"
  }
}

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
itemsNoitems. Array.
statusNostatus. String.
findingsNofindings. Array.
checkedAtNocheckedAt. String.
legalAdviceNolegalAdvice. Boolean.
limitationsNolimitations. Array.
fundsClearedNofundsCleared. Boolean.
rulesAppliedNorulesApplied. Boolean.
tenantContactedNotenantContacted. Boolean.
handoverCompletedNohandoverCompleted. Boolean.
evictionDeterminedNoevictionDetermined. Boolean.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior5/5

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

Beyond the annotations, the description discloses the paid x402 model ($0.05 USDC), the POST endpoint, and crucially that an unpaid call returns payment terms and does not execute — information an agent cannot get from readOnlyHint/idempotentHint/destructiveHint. It also adds an interpretive caveat that differences are not liability findings.

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, front-loaded with the purpose before the caveat, price, and payment behavior. Dense and readable; the endpoint string is the only mildly redundant element, though plausible for an HTTP-backed tool.

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?

Payment gating and the interpretive caveat are covered, and an output schema exists so return values need no explanation. But for a 14-parameter, deeply nested tool with zero required fields, the description gives no hint about which inputs are the baseline, which are the move-in list, or how the csv/file/json/text alternatives relate to the structured arrays.

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 coverage is 100%, but the schema descriptions are boilerplate type/length restatements, so the description's mention of room, name, condition, and count is the only semantic mapping to the inventory array fields. The roles of csv, file, json, text, items, rules, evidence, expected, documents, and obligations remain entirely unexplained.

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 first sentence names a specific verb ('Compare') and resource ('baseline inventory with the move-in list') and even lists the comparison axes (room, name, condition, count). It is clearly a distinct operation from the sibling checks (payment, document expiry, obligations), though it never names or contrasts an alternative explicitly.

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 by the comparison framing, and the caveat 'A difference is not a finding of liability' usefully frames how to interpret output. However there is no explicit guidance on when to use this versus siblings, nor on which of the 14 optional input parameters represent the baseline versus the move-in list.

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