Skip to main content
Glama

BRAINIAC Property Maintenance

Check a response service level

property-maintenance_response-sla-check
Read-onlyIdempotent

Compare a supplied response time with the service level for that stated urgency. No deadline is assumed when the caller does not supply one. Price $0.04 USDC. POST /api/v1/property-maintenance/response-sla-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": "property-maintenance_response-sla-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.
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?

Goes well beyond the annotations by disclosing the price ($0.04 USDC), the POST endpoint, and crucially that an unpaid call returns x402 payment terms and does not execute. That payment-gating behavior is a real operational fact an agent must know before invoking. It stops short of describing the comparison output, but an output schema exists to cover that.

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 the actual operation before pricing and transport details. The endpoint path is the least essential element but is compact and doesn't bloat the text.

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?

Payment gating, the no-deadline default, and rich annotations plus an output schema cover most needs. However, with 11 optional nested parameters, the description never explains which inputs establish the SLA baseline versus which supply the response times, leaving a real ambiguity for a complex tool.

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 nested objects. The description only implies that urgency drives the SLA lookup and adds no meaning about how slas, works, or requests interrelate, so baseline 3 applies.

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?

States a specific verb and resource: compare a supplied response time against the service level for a stated urgency. That is clearly distinct from siblings like contractor-quote-compare or invoice-validate, though the phrase 'supplied response time' is slightly ambiguous about which input field carries it.

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 purpose statement plus the rule that no deadline is assumed when the caller supplies none, which tells the agent the tool is safe to call with partial input. There's no explicit when-to-use/when-not-to-use guidance and no named alternative among the 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