Skip to main content
Glama

BRAINIAC Rental Operations

Check tenancy document completeness

rental-operations_tenancy-document-completeness
Read-onlyIdempotent

List the document kinds the caller marked as required and which of them were supplied. A jurisdiction name does not add a legal checklist. Price $0.04 USDC. POST /api/v1/rental-operations/tenancy-document-completeness. 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_tenancy-document-completeness"
  }
}

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

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Beyond the annotations (readOnly, idempotent, non-destructive, open-world), the description discloses two behaviors the annotations cannot: the call is metered at $0.04 USDC and an unpaid call returns x402 payment terms without executing. It also clarifies that passing a jurisdiction does not trigger a legal checklist, which prevents a reasonable misassumption. Return shape is left to the output schema, so no deduction there.

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 cost, endpoint, and payment behavior. Nothing is padded. The endpoint path and price read as boilerplate from a generated wrapper but still earn their place for an agent that must decide whether to pay.

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

Completeness4/5

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

For a tool with 14 optional parameters, a nested file object, and an output schema, the description covers purpose, cost, payment gating, and one key semantic caveat. What it omits is which inputs actually make the check meaningful (presumably requirements plus documents), leaving an agent to guess among a dozen optional arrays. Annotations and the output schema absorb the remaining burden.

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%, so all 14 parameters are already documented, and the schema descriptions are largely mechanical type/length restatements. The description adds only one piece of semantic guidance — that jurisdiction has no legal-checklist effect — which is genuinely useful but does not explain the roles of requirements, documents, or the many unrelated arrays (evidence, inventory, obligations). Baseline 3 applies.

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 opens with a concrete verb and resource: list the document kinds the caller marked as required and report which were supplied. That is specific enough to distinguish it from a mere expiry check. It stops short of naming a sibling by name, so the differentiation relies on the reader's inference.

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 phrase 'marked as required and which of them were supplied' — an agent can infer this is the completeness/coverage check. There is no explicit when-not guidance and no pointer to alternatives such as the expiry check or the obligation extract, which matters in a seven-tool family with overlapping tenancy concerns.

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