Skip to main content
Glama

BRAINIAC Rental Operations

Check tenant document expiry

rental-operations_tenant-document-expiry-check
Read-onlyIdempotent

Compare supplied expiry dates with a supplied as-of date. No as-of date means expiry is not judged, and a document number is reduced to its last four characters. Price $0.04 USDC. POST /api/v1/rental-operations/tenant-document-expiry-check. 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-document-expiry-check"
  }
}

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

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior4/5

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

Beyond the readOnly/idempotent annotations, the description discloses pricing ($0.04 USDC), the x402 payment gate (an unpaid call returns terms and does not run), and data handling (document numbers truncated to the last four characters). Those are real operational facts an agent cannot get from annotations. It does not describe result shape or failure modes beyond payment, which the output schema partly covers.

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 core comparison, then edge-case behavior, then cost and transport. Nothing is padded. The endpoint path is the least useful sentence but is brief.

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 14-parameter tool with nested documents, evidence, and expected arrays, the description covers the expiry logic and payment model but leaves the input-shape choice unexplained. An output schema exists, so return values need not be described. Adequate but with a clear gap around which payload form to supply.

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 the baseline is 3. The description adds meaning for only two things: asOf semantics and truncation of the document number field. It gives no guidance on the 14 parameters' interchangeable input containers (csv, json, text, file) or which documents fields drive the comparison.

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 states a specific verb and resource: compare supplied document expiry dates against a supplied as-of date. That is clearly distinct from sibling checks like document-completeness or move-in-readiness. It stops short of naming any sibling explicitly, so an agent must infer the boundary from the title alone.

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?

It gives one useful conditional: if no as-of date is supplied, expiry is not judged. That implies when the tool is and isn't meaningful, but there is no explicit guidance on when to choose this over the sibling completeness or obligation tools, and no prerequisites for the document inputs.

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