Skip to main content
Glama

BRAINIAC Vendor & Contractor Compliance

Prequalify a contractor

vendor-compliance_contractor-prequalification
Read-onlyIdempotent

Compare buyer qualification criteria with supplied vendor facts, documents, and evidence. The result does not award eligibility or query a registry. Price $0.05 USDC. POST /api/v1/vendor-compliance/contractor-prequalification. 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>",
      "requirements": "<requirements>"
    },
    "name": "vendor-compliance_contractor-prequalification"
  }
}

Input Schema

NameRequiredDescriptionDefault
asOfNoasOf, string. Optional.
vendorYesvendor, object. Required.
evidenceNoevidence, array. Optional.
documentsNodocuments, 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

A3.7/5.0
Behavior4/5

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

Annotations only declare read-only/idempotent/open-world; the description adds genuinely new behavior: a $0.05 USDC cost, the POST endpoint, and the x402 payment gate where an unpaid call returns payment terms and does not execute. That payment-gating disclosure is exactly the kind of hard constraint annotations cannot express. It does not say what a comparison result contains or how partial/missing evidence is handled.

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, front-loaded sentences: purpose first, then scope exclusion, price, endpoint, and payment behavior. Every sentence carries distinct information, though the raw endpoint path is the least useful line for an agent.

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 deeply nested tool with an output schema available, the description covers purpose, scope limits, cost, and payment failure mode, which is what an agent needs before invoking. Remaining gaps are secondary: no hint about how requirements are matched to documents/evidence, and no mention of result determinism despite the idempotent annotation.

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 schema already documents all six top-level parameters and their nested fields. The description adds only a loose mapping (vendor facts/documents/evidence vs. buyer criteria) and no guidance on semantics such as asOf, requirement kinds, or how requirement ids bind to document or evidence ids. Baseline 3 applies.

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?

"Compare buyer qualification criteria with supplied vendor facts, documents, and evidence" gives a specific verb and names the three input families, so the operation is unambiguous. The negative scope ("does not award eligibility or query a registry") sharpens it further. It stops short of distinguishing itself from close siblings like onboarding-precheck or document-completeness by name.

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 description implies the use case (buyer has criteria, vendor has supplied facts/documents/evidence) and excludes adjacent interpretations, but never states when to prefer this over contractor-closeout-check, document-completeness, or onboarding-precheck. Routing between siblings is left to inference.

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