Skip to main content
Glama

BRAINIAC Contract Operations

Group obligations by party

contract-operations_party-obligations

Group extracted obligations under the party named before shall, must, or agrees to. An obligation that names no party stays unassigned. Price $0.05 USDC. POST /api/v1/contract-operations/party-obligations. 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_party-obligations"
  }
}

Input Schema

NameRequiredDescriptionDefault
fileNo
textNo
clausesNo

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 burden and does disclose genuinely non-obvious behavior: a fixed price of $0.05 USDC, a 402 response for unpaid calls, and that failed payments mean the operation does not run. It also discloses the fallback rule for obligations with no named party. It does not say whether the call is read-only, idempotent, or rate limited.

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-loaded with the core grouping rule, followed by the unassigned-party edge case, pricing, and payment failure. Short sentences with no padding, though the raw endpoint path is largely redundant detail.

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?

A three-input, nested-schema tool with no output schema and no annotations needs the description to explain how inputs are supplied and what the grouped result looks like. It explains the grouping semantics but nothing about input selection or return shape, leaving the biggest practical gaps unaddressed.

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 optional, deeply nested parameters (file with mediaType/fileBase64, raw text, and a clauses array), yet the description never mentions any of the input modes. 'Extracted obligations' only loosely hints at the clauses input; an agent cannot tell from the prose whether to upload a PDF, pass raw text, or supply pre-parsed clauses.

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 transformation (group obligations by party) plus the concrete heuristic used (the party named before 'shall', 'must', or 'agrees to'). The phrase 'extracted obligations' implicitly positions it downstream of obligation-extract, though no sibling is named explicitly.

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 — it consumes already-extracted obligations, so it is not the entry point for a fresh document. There is no explicit statement of when to prefer it over obligation-extract or the other analysis siblings, and no exclusions.

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