Skip to main content
Glama

BRAINIAC Contract Operations

Describe contract changes

contract-operations_change-impact

Label meaningful version changes as a date, a stated period, an obligation verb, or an added or removed clause. The legal effect of a change is not decided. Price $0.06 USDC. POST /api/v1/contract-operations/change-impact. 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_change-impact"
  }
}

Input Schema

NameRequiredDescriptionDefault
baseYes
revisedYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior3/5

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

No annotations exist, so the description carries the full disclosure burden. It does several genuinely useful things: states the price ($0.06 USDC), the HTTP endpoint, and that unpaid calls return 402 without executing — real preconditions an agent must know. It says nothing about response shape, determinism, or input limits, and the legal-effect disclaimer is grammatically ambiguous about who is not deciding.

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?

Sentences are short and front-loaded, leading with the labeling semantics before the operational details. The price/endpoint/402 block is terse and earns its place for an agent that must handle payment failure. Minor waste in the standalone "The legal effect of a change is not decided" sentence, which could be folded in.

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 with deeply nested unlabeled inputs, no output schema, and no annotations, the definition is only partly sufficient. The output is at least inferable from the four label categories named up front, which partly offsets the absent output schema. The input side — the polymorphic base/revised objects — is where the gaps actually bite.

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% and both required parameters are nested objects with three-way polymorphism (file/text/clauses), yet the description adds almost no parameter meaning. The phrase "an added or removed clause" faintly gestures at the clauses input, and "version changes" implies base vs revised, but nothing clarifies when to send a PDF versus plain text, whether the three input modes are interchangeable, or that both objects share the same shape.

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 pair ("Label meaningful version changes") and enumerates the label categories: date, stated period, obligation verb, added/removed clause. That is far more informative than the title alone. It stops short of distinguishing itself from the sibling contract-operations_version-diff, which an agent could plausibly confuse this with.

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 rather than stated: an agent can infer this applies when comparing a base and revised version. The one explicit boundary is "The legal effect of a change is not decided," which correctly scopes out legal interpretation. There is no statement of when to prefer this over version-diff or any of the extract siblings, so the routing burden stays on the caller.

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