Skip to main content
Glama

BRAINIAC Vendor & Contractor Compliance

Build a vendor compliance report

vendor-compliance_report
Read-onlyIdempotent

Consolidate supplied vendor information, documents, attestations, evidence, and open items into one requirements report. External registries are not contacted. Price $0.08 USDC. POST /api/v1/vendor-compliance/report. An unpaid call returns the x402 payment terms and does not run.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "vendor-compliance_report"
  }
}

Input Schema

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

B3.4/5.0
Behavior2/5

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

The description adds genuinely valuable behavior beyond the annotations: a fixed price of $0.08 USDC, the fact that an unpaid call short-circuits and returns payment terms instead of running, and the endpoint. However, 'External registries are not contacted' asserts a closed-world, supplied-data-only scope while the annotations declare openWorldHint=true, so the two structured and unstructured signals are in tension and an agent cannot tell which governs verification behavior.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Four short sentences, purpose front-loaded, then the sourcing constraint, then price/endpoint, then the payment-failure mode. There is no filler and nothing repeated from the schema or annotations.

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?

An output schema exists, so return values need not be explained, and the description covers sourcing limits, cost, and payment behavior for a deeply nested 8-parameter tool. What remains thin is how `requirements`, `openItems`, and `evidence` relate at evaluation time, which matters given the nesting but is partly recoverable from the result schema.

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 parameter and nested field is already documented; the baseline of 3 applies. The description does conceptually group five of the eight top-level inputs (vendor, documents, attestations, evidence, open items) but adds no semantics for how they are matched against `requirements`, which is the tool's most consequential interaction.

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 names a specific verb and output: 'Consolidate supplied vendor information, documents, attestations, evidence, and open items into one requirements report.' That clearly separates it from the narrower sibling checks (closeout, prequalification, document-completeness) by naming the full set of consumed inputs and the single consolidated artifact, though it never explicitly says 'use this instead of X'.

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?

Usage is implied rather than stated: the tool takes supplied evidence and produces one consolidated requirements report, so an agent can infer it is the broad/full-report option. There is no explicit when-not guidance against the sibling checks, but the payment prerequisite ('Price $0.08 USDC ... an unpaid call returns x402 terms and does not run') is a useful operational precondition for calling it.

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