Skip to main content
Glama

BRAINIAC Vendor & Contractor Compliance

Check contractor closeout

vendor-compliance_contractor-closeout-check
Read-onlyIdempotent

Compare buyer closeout requirements with supplied documents and attestations. A passing result does not certify that the project is complete. Price $0.04 USDC. POST /api/v1/vendor-compliance/contractor-closeout-check. An unpaid call returns the x402 payment terms and does 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": {
      "requirements": "<requirements>"
    },
    "name": "vendor-compliance_contractor-closeout-check"
  }
}

Input Schema

NameRequiredDescriptionDefault
asOfNoasOf, string. Optional.
vendorNovendor, object. Optional.
documentsNodocuments, array. Optional.
projectNameNoprojectName, string, length 1 to 200. Optional.
attestationsNoattestations, array. Optional.
requirementsYesrequirements, array. Required.

Output Schema

NameRequiredDescriptionDefault
asOfNoasOf. String.
countsNocounts. Object.
vendorNovendor. Object.
purposeNopurpose. String.
summaryNosummary. String.
findingsNofindings. Array.
warningsNowarnings. Array.
checkedAtNocheckedAt. String.
assessmentNoassessment. String.
limitationsNolimitations. Array.
projectNameNoprojectName. String.
blocksWorkflowNoblocksWorkflow. Boolean.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior3/5

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

Adds real value beyond the annotations: the disclaimer that a passing result does not certify project completion, the $0.04 USDC price, and the fact that an unpaid call returns x402 payment terms without running. However it does not explain what drives a pass versus fail, or what happens with partial or malformed documents. Annotations cover read-only, idempotent, and non-destructive behavior, so the description is not carrying that load.

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 what the tool does, followed by the limitation, price, and endpoint. Mostly efficient, though the raw POST path plus the x402 sentence are operational rather than decisional detail.

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. Given the deep nested requirements schema and the compliance stakes, the description leaves a meaningful gap: how requirements of different kinds are evaluated and what a 'fail' result means. The disclaimers help but do not fully characterize the check.

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 every one of the 6 parameters, including nested requirement and document objects, is already documented. The description names the three main inputs at a high level, but adds no meaning about how requirement kinds are matched to documents or how attestation acceptance is used, so it stays at the baseline.

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 buyer closeout requirements with supplied documents and attestations.' That clearly separates closeout checking from a prequalification or document-completeness check, though it never names a sibling explicitly to route the agent.

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 closeout framing implies the right lifecycle moment, and the payment note signals the call may be gated, but there is no explicit when-to-use / when-not-to-use versus contractor-prequalification or subcontractor-payment-readiness. An agent must infer which of the sibling checks to call.

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