Skip to main content
Glama

BRAINIAC Contract Operations

Review a contract against supplied checks

contract-operations_compliance-review

Combine clause, obligation, deadline, renewal, checklist, party, and risk checks. checklist_satisfied means the supplied phrases were found. It is not a legal compliance determination. Price $0.12 USDC. POST /api/v1/contract-operations/compliance-review. Unpaid calls return 402 and do 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": "contract-operations_compliance-review"
  }
}

Input Schema

NameRequiredDescriptionDefault
asOfNo
fileNo
textNo
clausesNo
revisedNo
standardNo
checklistNo
withinDaysNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.3/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does meaningful work: it discloses the price ($0.12 USDC), the payment gate behavior (unpaid calls return 402 and do not run), and explicitly bounds its own output — checklist_satisfied only means the supplied phrases were found, not a legal compliance determination. Missing is any sense of the response shape or cost/size limits for large inputs, which is a notable gap given there is no output schema.

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?

Five short sentences, front-loaded with what the tool does and immediately following with the most decision-relevant caveats (output semantics, price, payment failure mode). The HTTP path is mildly redundant for an MCP caller but is the shortest way to state the operation and price together; nothing else wastes space.

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

Completeness2/5

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

For an eight-parameter, zero-coverage, no-output-schema tool with no annotations, the description covers cost and one output flag but leaves the input contract and return payload essentially undocumented. An agent can tell what the tool is for and what it costs, but not how to assemble a valid request or what it will get back.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% across eight nested parameters, and the description adds almost nothing: 'supplied phrases' vaguely gestures at the checklist/standard phrases arrays, and the named checks hint that clause, deadline, renewal, and party inputs exist, but asOf, withinDays, text/file, and revised are never explained. An agent must reverse-engineer input modes (inline text vs PDF base64 vs clause array vs revised version) entirely from 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 verb and resource are specific: it 'combines clause, obligation, deadline, renewal, checklist, party, and risk checks' over a contract, which clearly identifies it as the aggregate review tool relative to the single-check siblings. It stops short of naming which sibling to use when a narrower check is wanted, so an agent knows what it does but not precisely how it differs in scope from e.g. risk-summary.

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 by the word 'Combine' — this is the tool that runs all the checks at once rather than one at a time — but there is no explicit when-to-use/when-not-to-use statement or named alternative. The pricing and 402 note give practical preconditions but not selection guidance against the nine sibling tools.

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