Skip to main content
Glama

BRAINIAC Contract Operations

Extract contract clauses

contract-operations_clause-extract

Extract numbered clauses, parties, defined terms, and a governing-law sentence from supplied contract text or a text-based PDF. Each item keeps a source excerpt. Missing headings stay unavailable. Price $0.06 USDC. POST /api/v1/contract-operations/clause-extract. 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_clause-extract"
  }
}

Input Schema

NameRequiredDescriptionDefault
fileNo
textNo
clausesNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

With no annotations supplied, the description carries the full burden and does substantial work: it discloses the price ($0.06 USDC), the endpoint, that unpaid calls return 402 and do not execute, that each extracted item retains a source excerpt, and that missing headings stay unavailable. It stops short of describing the response envelope or non-payment error modes such as oversized/unsupported files.

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?

Five short sentences, each carrying distinct information: capability, output shape, edge case, price, transport and payment failure. Front-loaded with the capability and free of filler.

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?

Covers cost, transport, and the nature of returned items, which matters for a paid endpoint with no output schema. It is still incomplete for a tool with nested inputs: the purpose of the 'clauses' parameter and the structure of the returned payload are not addressed.

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, including a nested file object and a nested clauses array. The description maps only loosely onto file/text ('contract text or a text-based PDF') and never explains the 'clauses' array parameter or the media-type/size limits, leaving the most ambiguous input undocumented.

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?

States a specific verb (Extract) and enumerates exactly what is returned: numbered clauses, parties, defined terms, and a governing-law sentence. The input scope ('contract text or a text-based PDF') further distinguishes it from sibling extractors like deadline-extract and obligation-extract.

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 input description ('supplied contract text or a text-based PDF'), and 'text-based PDF' implicitly excludes scanned images, which is a useful constraint. However, there is no explicit when-to-use statement and no routing guidance against the many sibling extraction 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