Skip to main content
Glama

BRAINIAC Property Maintenance

Validate a maintenance invoice

property-maintenance_invoice-validate
Read-onlyIdempotent

Compare an invoice amount and scope with one linked quote. A difference is not an overcharge finding, and a stated paid status does not mean a payment was sent. Price $0.04 USDC. POST /api/v1/property-maintenance/invoice-validate. 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_invoice-validate"
  }
}

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.6/5.0
Behavior4/5

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

Annotations already cover safety (readOnly, idempotent, non-destructive, openWorld), and the description adds genuinely new behavior: a $0.04 USDC price, a payment gate where unpaid calls return x402 terms without executing, and semantic limits on what a returned difference or paid status means. That is real value beyond the structured data. It does not explain the output shape or how partial inputs are treated, which keeps it from a 5.

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 with no padding; the core comparison is front-loaded, followed by the interpretive caveats and then the commercial/transport facts. The price and endpoint sentences are dense but each carries information an agent needs. Slight scruffiness from mixing semantics, price and transport in one block.

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 tool with 11 optional params, several nested arrays and four mutually exclusive input channels, the description says nothing about how to choose or combine those inputs, which is the main failure mode. Return values are covered by the output schema, so that omission is acceptable. Adequate but leaves a real gap around input assembly.

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, including the nested quote, invoice, request, work, rules and SLA objects. The description adds nothing about the four alternative content channels (csv, json, text, file) or the asOf cutoff, so it meets only the baseline where the schema carries the load.

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 specific verb and resource pair: 'Compare an invoice amount and scope with one linked quote.' An agent knows exactly what operation it performs and that it is single-quote scoped, which implicitly separates it from catalog-wide analysis siblings. It stops short of naming any sibling tool explicitly, so differentiation is inferred rather than stated.

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 context is implied by 'one linked quote' and the interpretive caveats about differences and paid status, telling the agent what this tool does not conclude. There is no explicit when-to-use framing, no prerequisites (e.g. which input channel to supply), and no direction to alternatives among the seven sibling tools.

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