Skip to main content
Glama

BRAINIAC Property Maintenance

Analyze repair history

property-maintenance_repair-history-analyze
Read-onlyIdempotent

Count supplied requests for the same property and type. A repeat is reported at three or more. The count is not a finding that the property is unsafe. Price $0.04 USDC. POST /api/v1/property-maintenance/repair-history-analyze. 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_repair-history-analyze"
  }
}

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.
statusNostatus. String.
findingsNofindings. Array.
checkedAtNocheckedAt. String.
limitationsNolimitations. Array.
workOrderedNoworkOrdered. Boolean.
propertySafeNopropertySafe. Boolean.
legalComplianceNolegalCompliance. Boolean.
tenantContactedNotenantContacted. Boolean.
contractorDispatchedNocontractorDispatched. 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 read-only, idempotent, and non-destructive annotations, the description discloses the $0.04 USDC price, the POST endpoint, and the important x402 behavior that an unpaid call returns payment terms without running. The repeat threshold and non-safety caveat further clarify what the analysis does and does not establish.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is compact and front-loads the operation, grouping criterion, and repeat threshold. The safety caveat, price, endpoint, and unpaid-call behavior each add distinct information without unnecessary wording.

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?

The core analysis and payment behavior are adequately described, and the output schema removes the need to document return values here. However, for an 11-parameter tool with nested objects and multiple possible input containers, the absence of minimum-input requirements, input-source selection or precedence rules, and guidance on ancillary parameters leaves important invocation details to inference.

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 score applies. The description adds that requests are matched using their property and type values, but it does not explain how to choose among requests, csv, json, text, and file inputs or clarify the relevance of parameters such as asOf, rules, slas, works, quotes, and invoices.

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 gives a specific operation and scope: counting supplied requests that share a property and type, with a repeat reported at three or more. This makes the core function clear, but it does not explicitly differentiate the tool from siblings such as priority assessment or reporting.

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?

The grouping rule and repeat threshold imply that the tool is for identifying recurring repair requests. The statement that the count is not a safety finding limits interpretation, but there is no explicit when-to-use guidance or routing to an alternative for other repair-history questions.

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