Skip to main content
Glama

BRAINIAC Vendor & Contractor Compliance

Precheck vendor onboarding

vendor-compliance_onboarding-precheck
Read-onlyIdempotent

Compare a supplied vendor record, document list, and attestations with the buyer requirements. Missing, expired, failed, and unverified items are reported separately. Price $0.04 USDC. POST /api/v1/vendor-compliance/onboarding-precheck. 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": {
      "vendor": "<vendor>"
    },
    "name": "vendor-compliance_onboarding-precheck"
  }
}

Input Schema

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

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

A3.7/5.0
Behavior4/5

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

The annotations already declare readOnly, idempotent, non-destructive, and open-world, so the safety profile is covered. The description adds behavior the annotations cannot: a $0.04 USDC price, the POST endpoint, and the fact that an unpaid call short-circuits to payment terms instead of executing. It also says findings are bucketed into missing, expired, failed, and unverified. It does not describe determinism or output volume, so it is not quite a 5.

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 is compared before the result categories, price, endpoint, and payment failure mode. No filler. The endpoint path is marginally redundant with the tool name but is useful for direct HTTP callers.

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 complex nested schema with six top-level parameters and an output schema, the description covers purpose, expected input shape, output categorization, cost, and the payment failure mode. Return-value structure is correctly left to the output schema. Minor gap: it does not say whether absent documents or attestations are treated as missing rather than skipped.

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 input schema already documents every field, including nested vendor, documents, attestations, and requirements structures. The description only restates which three collections are compared and mentions requirements implicitly, adding no syntax or format guidance beyond the schema. Baseline 3 applies when the schema carries the semantics.

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 uses a specific verb and resource: it compares a vendor record, document list, and attestations against buyer requirements, and it names the four report categories. That is far more precise than a restatement of the title. It does not explicitly distinguish itself from siblings such as prequalification or document-completeness, so it falls short of a 5.

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 onboarding context implies when to call it: before onboarding, to validate a supplied vendor package. The payment gate (an unpaid call returns x402 terms and does not run) is a useful operational condition. However, it never states when to prefer a sibling like contractor-prequalification or document-completeness instead, so the guidance 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