Skip to main content
Glama

BRAINIAC Contract Operations

Extract contract obligations

contract-operations_obligation-extract

Extract sentences that use shall, must, agrees to, is required to, or undertakes to, and name the party stated before the verb. Sentences that only say may are not turned into obligations. Price $0.06 USDC. POST /api/v1/contract-operations/obligation-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_obligation-extract"
  }
}

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 supplied, the description carries the full burden and does well on the commercial/operational side: it discloses a $0.06 USDC price, the POST endpoint, and that unpaid calls return 402 without executing — material facts an agent must know before invoking. It stops short of stating that the operation is non-destructive/read-only and gives no sense of latency, limits, or response shape.

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 extraction rule is front-loaded in the first two sentences and the operational facts (price, endpoint, 402) follow compactly. Every sentence carries information, though the bare endpoint path adds little for an agent that already knows the tool name.

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?

There is no output schema, no annotations, and three undocumented input modes, so the description needed to do more than explain the matching heuristic. It is strong on what counts as an obligation but silent on how to supply input and what comes back, leaving real gaps for a paid, nested-schema tool.

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 with mediaType/fileBase64 and a clauses array, so the description must compensate — and it says nothing about them. An agent cannot tell from this text whether file, text, and clauses are alternatives or combinable, nor what format each expects.

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 uses a specific verb (extract) plus a precisely defined target (sentences with shall/must/agrees to/is required to/undertakes to, with the preceding party named), which is far more informative than the title alone. It does not, however, distinguish itself from siblings such as contract-operations_party-obligations, leaving an agent to infer the boundary.

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 inclusion/exclusion rule ('sentences that only say may are not turned into obligations') implicitly tells the agent when this tool is the right fit versus a broader clause extractor. There is no explicit statement of when to prefer it over siblings, and no guidance on choosing among the three 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