Skip to main content
Glama

BRAINIAC Property Maintenance

Compare contractor quotes

property-maintenance_contractor-quote-compare
Read-onlyIdempotent

Compare supplied quotes by price, stated completion days, scope, and exclusions. The lowest price is not a recommendation, and different currencies are not converted. Price $0.05 USDC. POST /api/v1/property-maintenance/contractor-quote-compare. 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_contractor-quote-compare"
  }
}

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
groupsNogroups. 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

A4.1/5.0
Behavior5/5

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

Goes well beyond the annotations by disclosing three material behaviors: prices across currencies are not converted, cheapest is not a recommendation, and the tool is a paid endpoint ($0.05 USDC) that returns x402 payment terms without running when unpaid. The annotations already cover read-only/idempotent/non-destructive, and the description adds the payment and interpretation semantics that matter for correct use.

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-loaded with the purpose and comparison axes, followed by interpretation caveats and then the payment/endpoint logistics. Every sentence carries information, though the raw endpoint path is somewhat procedural clutter for an agent that already has the tool handle.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With an output schema present, return values need no explanation, and the description adequately covers behavior and payment flow. The only real gap for an 11-parameter tool with nested objects is guidance on which input format (csv/json/text/file) to supply and how the nested quotes/slas/rules arrays are used.

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 coverage is nominally 100%, so baseline is 3, but the schema property descriptions are tautological ('csv, string, length 0 to 200000'). The description names the comparison fields but never clarifies the multiple alternative input channels (csv, json, text, file) or how the quotes array should be populated, leaving real ambiguity that the schema does not resolve.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb (compare) and resource (contractor quotes) with the exact comparison axes: price, stated completion days, scope, and exclusions. This is plainly distinct from the sibling analysis tools (invoice-validate, priority-assess, sla-check, etc.), so an agent can select it without opening the schema.

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 only implied: it applies when you already have quotes to compare ('supplied quotes'), but the definition never states when to prefer this over the sibling tools or what input prerequisites are. The notes about lowest price not being a recommendation and currencies not being converted are behavioral caveats, not when-to-use guidance.

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