Skip to main content
Glama

BRAINIAC Contractor Payment Application Audit

Audit contractor payment applications

construction-commercial_contractor-payment-application-audit

Independently check a contractor payment application against the schedule of values, measured work, approved variations, previous certificates, retention rules, and deductions. Unsupported claims, duplicated work, unapproved variations, retention errors, and certificate mismatches are adjusted with calculation evidence. The recommended payable amount is for review only. Price $0.04 USDC. POST /api/v1/construction-commercial/contractor-payment-application-audit. Unpaid calls return 402 and do not run.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "contract": "<contract>",
      "schedule_of_values": "<schedule_of_values>",
      "payment_application": "<payment_application>"
    },
    "name": "construction-commercial_contractor-payment-application-audit"
  }
}

Input Schema

NameRequiredDescriptionDefault
contractYes
deductionsNo
variationsNo
measured_workNo
schedule_of_valuesYes
payment_applicationYes
previous_certificatesNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

With no annotations, the description carries the full behavioral burden. It discloses that unsupported claims and errors are adjusted with calculation evidence, that the recommended payable amount is for review only, and that unpaid calls return 402 and do not run. It does not disclose auth requirements or whether the tool stores results, but the behavioral picture is substantially clearer than the schema alone.

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 description is front-loaded with the core purpose and audit checks, then adds operational details about review status, price, endpoint, and unpaid-call behavior. The sentences are efficient, though the endpoint and price information could be considered metadata rather than descriptive guidance.

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 complex audit tool with 7 nested parameters, no annotations, and no output schema, the description covers the process and invocation constraints well. It remains incomplete on parameter semantics and does not describe the response structure beyond mentioning the recommended payable amount and calculation evidence.

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 0%, so the description must compensate. It meaningfully names the domain artifacts used in the audit, such as schedule of values, measured work, approved variations, previous certificates, and deductions, which helps map top-level parameters to their roles. However, it does not explain nested field semantics, required fields, or unit conventions, leaving a significant gap for 7 nested parameters.

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?

The description states a specific verb and resource: independently check a contractor payment application. It further specifies the artifacts it audits against, including schedule of values, measured work, approved variations, previous certificates, retention rules, and deductions. This is far more specific than a generic 'audit' tool.

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?

The intended use is implied by the detailed audit scope, but there is no explicit when-to-use or when-not-to-use guidance. No alternatives are named, so the agent must infer this is the right tool for contractor payment application audits.

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