Skip to main content
Glama

BRAINIAC Contract Operations

Check for missing provisions

contract-operations_missing-clause-check

Compare the contract with a checklist or with provisions supplied for a named standard. A standard name alone does not create required clauses, and similar wording is not inferred. Price $0.05 USDC. POST /api/v1/contract-operations/missing-clause-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_missing-clause-check"
  }
}

Input Schema

NameRequiredDescriptionDefault
fileNo
textNo
clausesNo
standardNo
checklistNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior4/5

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

With no annotations, the description carries the burden and does add non-obvious behavior: it costs $0.05 USDC, unpaid calls return 402 and do not execute, and matching is literal ("similar wording is not inferred"). The payment/auth gate and exact-match semantics are exactly the kind of detail the schema cannot convey. It still omits what a successful response contains or what happens when every input is empty.

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?

Front-loads the core comparison, then the matching caveat, then cost and endpoint. Every sentence carries information, though the raw POST path partly restates the tool name and costs a little space given the missing parameter explanation.

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?

For a tool this complex (nested objects, upload-or-text input, no output schema, all parameters optional), the definition covers purpose, cost, payment failure, and matching strictness, but leaves the interaction between inputs and the return value unaddressed. An agent can guess how to call it but not what to expect back or which input combination is valid.

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 5 parameters, including nested file, clauses, checklist, and standard objects, so the description must compensate and largely does not. It explains that a standard needs provisions and that a checklist is an alternative, but never distinguishes file vs text for the contract, never explains the clauses input, never explains the phrases field used for matching, and never says whether checklist and standard can be combined.

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?

States a specific verb/resource pairing: "Compare the contract with a checklist or with provisions supplied for a named standard." That distinguishes it from obligation-extract or compliance-review by making the comparison baseline explicit. It stops short of naming a sibling to route away from, which keeps it at 4 rather than 5.

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?

Gives a real precondition: you must supply a checklist or explicit provisions, and "a standard name alone does not create required clauses." That is genuine when-to-use/when-it-won't-work guidance an agent wouldn't get from the schema. It doesn't state the converse selection case (e.g. use compliance-review when you want judgment rather than coverage), so it isn't a full routing rule.

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