Skip to main content
Glama

BRAINIAC Property Maintenance

Assess maintenance priority

property-maintenance_priority-assess
Read-onlyIdempotent

Apply a fixed order: a safety keyword, then a stated emergency, urgent, or routine urgency. A missing urgency is not treated as routine, and the result is not a safety verdict. Price $0.04 USDC. POST /api/v1/property-maintenance/priority-assess. 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_priority-assess"
  }
}

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

B3.4/5.0
Behavior4/5

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

Beyond the readOnly/idempotent/non-destructive annotations, the description discloses determinism ('a fixed order'), an explicit non-goal ('not a safety verdict'), the missing-urgency edge case, and the payment contract: $0.04 USDC, POST endpoint, and that an unpaid call returns x402 payment terms without executing. The only omission is what the response payload contains, which the output schema 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?

The precedence rule is correctly front-loaded, and each remaining sentence carries distinct payload (caveats, price, endpoint, unpaid-call behavior) with no filler. The raw POST path is slightly redundant against the generated transport metadata, but it costs little.

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?

Behavior, cost, and failure mode are well covered and the output schema handles return values, but this is an 11-parameter tool with deeply nested arrays and the description says nothing about input shape or which input channel to supply. An agent knows how it will be charged and what rule applies, but not which parameters are required to make the rule evaluable.

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 the nested request/quote/invoice/SLA objects, making 3 the baseline. The description adds no mapping from its concepts (safety keyword, urgency) to specific fields like requests[].urgency or slas[].urgency, nor does it say when to use csv/text/json/file inputs.

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 concrete decision rule (a safety keyword first, then a stated emergency/urgent/routine urgency) and explicitly bounds the outcome with 'the result is not a safety verdict', which an agent can distinguish from a classifier or SLA checker. It never names an actual sibling tool, so routing to property-maintenance_request-classify or response-sla-check is left to inference.

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 relative to the sibling tools; the only guidance is internal to the tool's own evaluation order. 'A missing urgency is not treated as routine' is a behavioral rule, not a selection criterion, so an agent still cannot tell why it would pick this over request-classify.

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