Skip to main content
Glama

BRAINIAC Vendor & Contractor Compliance

Check vendor document completeness

vendor-compliance_document-completeness
Read-onlyIdempotent

Compare a supplied document inventory with a buyer requirements list. Files are not fetched, and a present document is not treated as verified content. Price $0.03 USDC. POST /api/v1/vendor-compliance/document-completeness. 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": {
      "documents": "<documents>",
      "requirements": "<requirements>"
    },
    "name": "vendor-compliance_document-completeness"
  }
}

Input Schema

NameRequiredDescriptionDefault
asOfNoasOf, string. Optional.
documentsYesdocuments, array. Required.
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.5/5.0
Behavior5/5

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

Beyond the annotations, the description discloses the price, HTTP endpoint, x402 payment gate, and that an unpaid call returns payment terms without executing. It also clarifies two non-obvious behavioral limits: no file retrieval and no content verification.

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?

The description is four short sentences, front-loads the comparison purpose, then adds only operationally relevant constraints and payment behavior. Every sentence contributes useful information without repetition.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the full input schema and an existing output schema, the description supplies what the structured fields do not: non-fetching behavior, the non-verification caveat, pricing, endpoint, and payment-gated execution. That is sufficient for an agent to know how and when the tool will run.

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 carries the detailed parameter documentation. The description only conceptually maps to documents and requirements and adds no field-level matching rules or syntax beyond what the schema provides.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific verb and resource: compare a supplied document inventory against a buyer requirements list. It also immediately distinguishes this completeness check from content verification by saying files are not fetched and a present document is not treated as verified.

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?

It gives a clear usage boundary: this is for comparing an inventory against requirements, not for fetching files or verifying document contents. It does not explicitly name sibling alternatives or a precise when-to-use-exactly condition, so it falls short of full routing guidance.

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