legal-intake-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| load_documentA | Load a contract and return its normalised text with a citation anchor on every paragraph, plus the detected language mix. Start here. Returns the format, page count where the format has pages, per paragraph text direction for correct rendering of mixed Arabic and English, any encoding repairs that were applied, and any warnings such as a PDF with a lossy or missing text layer. Paragraph anchors look like "P12" and are the same anchors every other tool reports. |
| segment_clausesA | Split the document into numbered clauses and headings, handling English and Arabic numbering conventions. English decimal (1, 1.1, 1.1.1), lettered and roman sub items, and the Arabic conventions المادة (٣), البند الأول, standalone ordinals أولاً and ثانياً, and Arabic decimal ٣-٢ written with a hyphen. Each clause gets a stable anchor such as "C14", its label exactly as the document writes it, an ASCII normalised label for comparison, its nesting depth, its parent clause, and the paragraph anchors it covers. Cite these anchors so the reader can find the exact clause. |
| extract_datesA | Extract every date, classify what it is for, and compute the deadlines that follow from it. Handles Gregorian and Hijri, Arabic-Indic and Persian digits, and month names in the Egyptian and Gulf, Levantine and Iraqi, and Hijri naming traditions. Each date reports its calendar, an ISO value, the role it plays (execution, commencement, term_end, renewal, notice, payment, delivery, signature) and the wording that justified that role. Hijri dates are converted with the tabular civil calendar and labelled as such, and where the contract states its own Gregorian equivalent any divergence is reported rather than resolved. Also returns notice periods found in the text and, where a fixed date anchors them, computed deadlines such as the date by which notice of non-renewal must be given. |
| extract_partiesA | Extract the parties, their defined terms and roles, their registration identifiers and addresses, and the signatories with their titles, each with an anchor. Reads both drafting traditions: the English numbered recital with a bracketed defined term, and the Arabic ordinal block with the ويشار إليه formula and the ويمثلها في التوقيع representative clause, which names the person who actually bound the company and is often the only place they are named. |
| find_clausesA | Find the clauses that deal with a legal concept and return their real text with anchors, so the model reviews the actual wording instead of a summary of it. Supported concepts: auto_renewal, unilateral_termination, penalty, governing_law, arbitration, confidentiality, non_compete, limitation_of_liability, notice, payment_terms, force_majeure, assignment, entire_agreement. Matching runs over an Arabic aware folded copy of the text, so a clause still matches whichever way it spells a term. Pass |
| document_summaryA | Build a structured skeleton of the contract for the model to reason over: parties and signatories, the term and whether it renews automatically, the obligations with the party bound by each, and the anchors of clauses that commonly need a closer look (auto renewal, unilateral termination, penalties, non compete, liability caps, arbitration). It returns structure and citations only. It contains no legal opinion, no risk rating and no recommendation, because those are the reviewing lawyer's to make. |
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/omarnagy91/legal-intake-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server