Skip to main content
Glama

BRAINIAC Property Maintenance

Report property maintenance

property-maintenance_report
Read-onlyIdempotent

Combine supplied request classes, safety keywords, quote comparisons, service levels, repeat repairs, and invoice differences. The report does not call a property safe or dispatch a contractor. Price $0.12 USDC. POST /api/v1/property-maintenance/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": "property-maintenance_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.
slasNoslas, array. Optional.
textNotext, string, length 0 to 200000. Optional.
rulesNorules, array. Optional.
worksNoworks, array. Optional.
quotesNoquotes, array. Optional.
invoicesNoinvoices, array. Optional.
requestsNorequests, array. Optional.

Output Schema

NameRequiredDescriptionDefault
itemsNoitems. Array.
groupsNogroups. Array.
ordersNoorders. Array.
statusNostatus. String.
historyNohistory. Array.
serviceNoservice. Array.
findingsNofindings. Array.
invoicesNoinvoices. Array.
checkedAtNocheckedAt. String.
prioritiesNopriorities. Array.
limitationsNolimitations. Array.
safetyCountNosafetyCount. Number.
workOrderedNoworkOrdered. Boolean.
outsideCountNooutsideCount. Number.
patternCountNopatternCount. Number.
propertySafeNopropertySafe. Boolean.
requestCountNorequestCount. Number.
escalateCountNoescalateCount. Number.
legalComplianceNolegalCompliance. Boolean.
tenantContactedNotenantContacted. Boolean.
contractorDispatchedNocontractorDispatched. Boolean.
invoiceDifferenceCountNoinvoiceDifferenceCount. Number.

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 annotations (readOnly, idempotent, openWorld, non-destructive), the description discloses real operational traits: a $0.12 USDC price, the POST /api/v1/property-maintenance/report endpoint, and the x402 behavior that an unpaid call returns payment terms and does not execute. It also bounds the output's authority. It does not describe payload size limits or latency for the large file input, which would complete the picture.

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 what gets combined, followed by the scope limit and then the payment mechanics. Nothing is redundant, though the telegraphic list style is terse and the endpoint string sits oddly between cost and payment behavior.

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?

With 11 optional parameters, nested objects and an output schema, the return shape is covered by the schema and payment behavior is covered by the description. What is missing is guidance on which inputs are needed for a meaningful report, how csv/json/text/file interact with the structured arrays, and what happens if the call is made with no inputs at all.

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 schema already documents all 11 parameters and their nested fields, making 3 the baseline. The description's enumeration of evidence classes loosely maps to requests/quotes/slas/works/invoices and hints at the csv/json/text/file ingestion paths, but it never explains the relationship between the raw input formats and the structured arrays.

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 names a concrete verb ('combine') and enumerates the exact evidence classes it aggregates (request classes, safety keywords, quote comparisons, service levels, repeat repairs, invoice differences), which maps clearly onto the sibling analyses. It also draws a boundary ('does not call a property safe or dispatch a contractor'), so an agent can tell this is the aggregating/reporting layer rather than a decision tool. It stops short of explicitly naming any sibling it replaces.

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 aggregation framing: gather all the sub-analyses into one report. There is a useful negative constraint (no safety verdict, no contractor dispatch), but no explicit 'use this when you need a consolidated view; use the individual sibling tools when you need one dimension'. No prerequisites or input minimums are stated.

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