Skip to main content
Glama

BRAINIAC Contract Operations

Extract contract deadlines

contract-operations_deadline-extract

Extract stated periods, notice periods, and unambiguous calendar dates. Slash dates are not guessed, and a deadline is not created when the text gives no number or date. Price $0.05 USDC. POST /api/v1/contract-operations/deadline-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_deadline-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, the description carries the full burden and does well: it discloses the cost ($0.05 USDC), the transport (POST endpoint), the failure mode (402 on unpaid calls, which do not run), and a precision policy (no guessing slash dates, no deadline fabricated without a number or date). It does not describe the response shape or what happens with malformed input.

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?

Four short sentences, front-loaded with the extraction scope and followed by the precision rules and the commercial/transport facts. No filler, though the endpoint string is close to redundant with 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?

No output schema exists, so the description should convey what comes back, and it does not — an agent knows deadlines are extracted but not the result structure. Combined with the total absence of input guidance for a nested three-parameter schema, the definition is adequate but leaves real gaps.

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?

Three parameters with 0% schema description coverage, including a nested file object and a clauses array, and the description says nothing about them. An agent cannot tell from the text that it may supply a PDF, plain text, or pre-split clauses, nor how those inputs interact.

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 verb and resource: 'Extract stated periods, notice periods, and unambiguous calendar dates.' The scope is narrow enough to separate it from clause-extract and obligation-extract siblings, though it never names them 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 only implied by the scope of what it extracts; there is no explicit statement of when to prefer this over obligation-extract or clause-extract, nor any prerequisite guidance. The precision rules ('slash dates are not guessed') hint at when it is appropriate but do not constitute routing guidance.

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