Skip to main content
Glama

BRAINIAC Vendor & Contractor Compliance

Check subcontractor payment readiness

vendor-compliance_subcontractor-payment-readiness
Read-onlyIdempotent

List missing payment documents and caller-supplied open items. This check does not release a payment or rerun sanctions, wage, or certificate screens. Price $0.04 USDC. POST /api/v1/vendor-compliance/subcontractor-payment-readiness. 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_subcontractor-payment-readiness"
  }
}

Input Schema

NameRequiredDescriptionDefault
asOfNoasOf, string. Optional.
vendorNovendor, object. Optional.
documentsNodocuments, array. Optional.
openItemsNoopenItems, array. Optional.
projectNameNoprojectName, string, length 1 to 200. 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

A4.1/5.0
Behavior5/5

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

Beyond the annotations (readOnly, idempotent, non-destructive), the description discloses cost ($0.04 USDC), the HTTP endpoint, and the critical failure mode: an unpaid call returns x402 payment terms and does not execute. That payment-gating behavior is the kind of context annotations cannot convey and is exactly what an agent needs before calling.

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 purpose then exclusions then commercial/transport details. Every sentence carries information; the endpoint path is mechanical but justified for a pay-per-call API.

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?

For a tool with a deeply nested input schema and an existing output schema, the description covers purpose, non-goals, cost, and payment failure behavior. It does not explain how the supplied requirements drive the result or what the response list looks like, but the output schema carries the latter.

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 required `requirements` array and nested vendor/document/openItems objects are already documented structurally. The description only adds the semantic hint that open items are "caller-supplied" rather than computed, which is marginal value over the schema.

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?

The description opens with a specific verb and resource: "List missing payment documents and caller-supplied open items." It also sharply scopes what the tool is not (payment release, sanctions/wage/certificate screens), which lets an agent separate it from heavier compliance checks, though no sibling is named explicitly.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Clear negative guidance is given: this does not release a payment and does not rerun sanctions, wage, or certificate screens, which tells the agent when to reach for a different tool. It lacks a positive "use this when" statement or named alternatives, so the routing is implied rather than explicit.

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