cuad-audit
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| ANTHROPIC_API_KEY | No | Anthropic API key for LLM calls in audit_clause and eval-verdicts |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_clausesA | 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. |
| get_standardA | Return the company standard (playbook) for a clause type: positions P1-P6 with provenance. The standard is data derived from the clause library, not legal advice; see scope_claim in the result. |
| audit_clauseA | Audit a clause against the company standard with grounded citations. Verdicts: acceptable / risky / off-standard (each carries a citation chunk_id resolved by the server to the exact precedent span); insufficient-grounding (evidence too weak OR the verdict failed the faithfulness check — escalate to a human, do NOT guess a verdict yourself); escalate-infra (API failure — retry later; not a judgment about the clause). Relay abstentions verbatim; they are first-class results. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/master997/luminance'
If you have feedback or need assistance with the MCP directory API, please join our Discord server