Skip to main content
Glama
Sign In
cuad-audit

cuad-audit

by master997
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

search_clauses

Search a library of liability clause precedents to find matches for a given clause text. Returns relevant chunks with source details and similarity scores.

Instructions

Search the precedent clause library (CUAD liability spans).

Returns chunks with stable chunk_ids, source contract, char offsets and scores. If evidence is too weak (status: "below_threshold"), that is an abstention, not an error: do NOT retry with rephrased queries to force a result — relay the abstention. top_scores shows how far below the threshold the best matches were.

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": {
      "query": "<query>"
    },
    "name": "search_clauses"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryYesFull clause text to find precedents for. Pass the complete clause: short paraphrases score lower against the evidence gate and abstain more often (the gate is calibrated on full clause texts).
clause_typeNoClause lane to audit against. Only 'liability' is implemented.liability
kNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.3/5.0
Behavior4/5

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

With no annotations, the description covers key behaviors: returns stable chunk IDs, source, offsets, scores; explains 'below_threshold' means abstention (not error); mentions top_scores. No destructive implications or contradictions.

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?

Four short sentences, front-loaded with the main purpose, each sentence adds specific value. No fluff or repetition.

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?

Given no output schema or annotations, the description is fairly complete but lacks explanation for the k parameter (only in schema with constraints) and does not fully describe the return structure beyond listing fields. Could be more thorough.

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

Parameters4/5

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

Schema coverage is 67%, and the description adds value: warns against short paraphrases for query, clarifies clause_type constraint. The k parameter lacks description, but overall the description enriches the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool searches a precedent clause library for CUAD liability spans, and lists what it returns (chunks with IDs, source, offsets, scores). It distinguishes from sibling tools by being explicitly a search function.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Provides strong usage guidance: warns against retrying on weak evidence, advises passing complete clause texts to avoid abstentions. Does not explicitly contrast with siblings, but gives actionable instructions.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools