Skip to main content
Glama

BRAINIAC Contract Operations

Check renewal wording

contract-operations_renewal-risk-check

Read renewal and expiration wording that is actually printed. A notice date is calculated only from a stated expiration date and a stated notice period. Renewal wording is flagged as a potential risk, not a legal conclusion. Price $0.04 USDC. POST /api/v1/contract-operations/renewal-risk-check. 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_renewal-risk-check"
  }
}

Input Schema

NameRequiredDescriptionDefault
asOfNo
fileNo
textNo
clausesNo
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 explanatory burden, and it discloses useful behavior: it reads only printed wording, does not infer, frames its output as a potential risk rather than a legal conclusion, charges $0.04 USDC, and returns 402 without running when unpaid. It does not describe the response contents, which matter because no output schema exists. These disclosures are strong for payment and scope semantics but incomplete for return behavior.

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?

The description is front-loaded with the core purpose and scope constraints, then the operational facts of price and endpoint. Each sentence contributes something, though the bare endpoint and price sentences could be tighter. Nothing is redundant.

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 a five-parameter tool with nested inputs, no annotations, no output schema, and 0% schema coverage, the description is materially incomplete. It says nothing about which inputs to supply, what withinDays or asOf control, or what the agent receives back, leaving the agent to guess at invocation details.

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% for five parameters, including a nested file object and a clauses array, so the description must compensate, yet it does not. It never mentions asOf, withinDays, file, text, or clauses, nor that the three input modes are presumably alternatives. Only an oblique hint about expiration date and notice period relates to the date parameters.

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 operation: reading renewal and expiration wording that is printed in a document and flagging renewal wording as a risk. This distinguishes it from siblings such as deadline-extract or risk-summary, which perform broader extraction. It never names an alternative tool or tells the agent when to choose this one over those siblings.

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 intended use is implied by the explanatory note that a notice date is computed only from a stated expiration date and notice period, which signals the tool's narrow scope. The description offers no explicit when-to-use guidance, no exclusions, and no advice on how to choose among the file, text, or clauses input modes.

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