Skip to main content
Glama

BRAINIAC Property Maintenance

Classify a maintenance request

property-maintenance_request-classify
Read-onlyIdempotent

Classify a stated type only from an explicit token, and flag a documented safety keyword for a person to review. An unrecognized word is left unrecognized. Price $0.04 USDC. POST /api/v1/property-maintenance/request-classify. 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_request-classify"
  }
}

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?

Beyond the annotations (read-only, idempotent, non-destructive), the description adds high-value behavior: pricing at $0.04 USDC, that an unpaid call returns x402 payment terms and does not execute, and the conservative classification policy. This material context is not captured by annotations and materially affects how an agent should invoke the tool.

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?

Front-loads the behavioral rule, then payment and endpoint details. Tight and readable; the endpoint path and price earn their place for an agent that must handle payment, with little wasted 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?

An output schema exists, so return values need not be explained. However, for an 11-param nested tool with multiple optional input shapes (text/csv/json/file/requests), the description never clarifies which to use, leaving a meaningful gap in invocation guidance.

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 params. The description adds no meaning about which inputs (text, csv, file, requests, slas, rules, quotes, etc.) are used or how they compose. Baseline 3 is appropriate given the schema does the heavy lifting.

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 (classify) and resource (a maintenance request's stated type), with the distinctive constraint that classification comes 'only from an explicit token.' This distinguishes it from siblings like priority-assess, though it does not name alternatives directly.

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?

Conveys the classification rule (explicit token only, unrecognized stays unrecognized) and the review-flagging behavior, but offers no explicit when-to-use guidance or routing versus siblings like request vs priority tooling. Usage is implied rather than 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