Skip to main content
Glama

BRAINIAC Rental Operations

Check first-rent payment evidence

rental-operations_first-rent-payment-check
Read-onlyIdempotent

Compare first-rent evidence with the expected amount, currency, and reference. A payment instruction is not treated as cleared funds. Price $0.04 USDC. POST /api/v1/rental-operations/first-rent-payment-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_first-rent-payment-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
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

B3.3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, and the description goes well beyond them: it discloses the pricing gate ($0.04 USDC via x402), states that an unpaid call returns payment terms and 'does not run', and adds the substantive semantic rule that a payment instruction is not treated as cleared funds. What is missing is how partial or mismatched evidence is reported (tolerance, missing-item handling), which the output schema may cover.

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?

The comparison rule is front-loaded, followed by the semantic caveat, price, endpoint and payment-gate behavior, all in short sentences with no padding. The HTTP path is arguably redundant detail for an agent that only needs name and arguments, which keeps it from a 5.

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

Completeness2/5

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

For a 14-parameter, deeply nested tool with zero required parameters, the description explains only the evidence-versus-expected comparison and leaves the large optional input bundle (documents, inventory, obligations, rules, requirements, file/csv/json/text) unexplained. An agent cannot tell from the description which of these actually influence the verdict or what happens when only a subset is supplied. The existence of an output schema offsets the missing return-value explanation but not the missing input-purpose coverage.

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%, so the baseline is 3. The description does add meaning by implying the core comparison is between the 'evidence' collection and the 'expected' collection on amount, currency and reference. It says nothing about the other eleven parameters (documents, inventory, obligations, rules, requirements, jurisdiction, asOf, csv/text/json/file), so no extra semantics are added there.

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 first-rent evidence with the expected amount, currency, and reference.' That is far more precise than the title alone and distinguishes it from the deposit-evidence sibling by naming 'first-rent'. It stops short of explicitly contrasting with rental-operations_deposit-payment-evidence-check, so it is not a 5.

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 when-to-use or when-not-to-use guidance and no named alternative. An agent is not told how this differs in practice from the deposit-payment-evidence-check or what inputs are prerequisites for a meaningful result. The only usage-adjacent statement is the negative rule about payment instructions, which is a judging rule rather than invocation guidance.

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