Skip to main content
Glama

BRAINIAC Contract Operations

Compare contract versions

contract-operations_version-diff

Compare two supplied contract versions by clause number or heading. Whitespace and letter case alone are not reported. Clauses are not matched by meaning. Price $0.08 USDC. POST /api/v1/contract-operations/version-diff. Unpaid calls return 402 and do not run.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "base": "<base>",
      "revised": "<revised>"
    },
    "name": "contract-operations_version-diff"
  }
}

Input Schema

NameRequiredDescriptionDefault
baseYes
revisedYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

With no annotations at all, the description carries real weight and does so: it discloses the normalization rule (whitespace/case differences suppressed), the non-semantic matching limit, the $0.08 price, the POST endpoint, and that unpaid calls return 402 without executing. The main omission is any hint of the response shape or how added/removed clauses are labeled.

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?

Every sentence earns its place: the core operation leads, then the two matching caveats, then pricing and transport details. No filler and no repetition of the schema.

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 paid, mutation-free but deeply structured tool with no output schema and no annotations, the definition covers cost and failure mode well but says nothing about what the diff result contains or how to choose among the file, text, and clauses input shapes. Adequate, not complete.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 0% and both parameters are deep nested objects, so the description would ideally clarify the three input modes (file, text, clauses) and the base-vs-revised direction. It only implies clause-based input via 'by clause number or heading' and leaves the file/text alternatives and mutual exclusivity unaddressed.

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 verb and resource ('compare two supplied contract versions') and adds the matching basis ('by clause number or heading'). That is enough to separate it from clause-extract or compliance-review siblings, though it never explicitly names an alternative.

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 'compare two supplied contract versions', and the boundary 'Clauses are not matched by meaning' tells the agent what this tool will not catch. There is no explicit statement of when to prefer a sibling or what prerequisites the caller must satisfy before paying.

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