Skip to main content
Glama

BRAINIAC Contract Operations

Summarize contract wording risks

contract-operations_risk-summary

Flag renewal, indemnity, unlimited-liability, and termination-for-convenience wording that is present in the text. These are potential risks, not a legal opinion or a risk score. Price $0.06 USDC. POST /api/v1/contract-operations/risk-summary. 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_risk-summary"
  }
}

Input Schema

NameRequiredDescriptionDefault
fileNo
textNo
clausesNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/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.06 USDC), the HTTP endpoint, and the exact failure mode (unpaid calls return 402 and do not run). It also pre-empts misinterpretation of results by stating the output is not a legal opinion. Gaps remain — no statement of idempotency, latency, or what the flags look like structurally — but the payment and execution behavior is well covered.

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 the substantive capability and followed by the scope disclaimer and then operational details (price, endpoint, 402). Every sentence carries information, though the bare endpoint string and price could arguably be compressed into a single operational sentence.

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

Completeness3/5

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

The commercial and failure semantics are complete, but for a tool with three undocumented, partly nested input parameters and no output schema, the description says nothing about the input modes or the shape of the returned flags. An agent can tell what the tool does and what it costs, but not how to assemble a valid request.

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 three parameters, one of which is a nested file object (mediaType/fileBase64/filename) and one a nested clause array. The description never mentions that input may be supplied as an uploaded PDF, raw text, or a pre-parsed clause array, nor that all three are formally optional and at least one is presumably needed. This leaves the agent to guess the input contract 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 first sentence names a precise verb ('Flag') and enumerates the exact wording categories targeted (renewal, indemnity, unlimited-liability, termination-for-convenience), and the following sentence bounds the output as presence-detection rather than a legal opinion or score. That clearly distinguishes it from a scoring or review tool, though it never names or differentiates itself from siblings like renewal-risk-check or compliance-review.

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 context is implied by the scoping note that these are 'potential risks, not a legal opinion or a risk score,' which tells the agent what class of task this fits. However, there is no explicit when-to-use guidance and no reference to an alternative tool for a full risk score or per-clause review, so the agent must infer routing from sibling names alone.

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