Legal counsel for AI products and agents (admitted in DC): scope, conflicts, engagement, intake.
Scored across 8 tools
Each tool maps to a distinct workflow stage (scope, conflict, engagement, intake, feature review, Q&A, status, trigger list), and descriptions reinforce the ordering. The only soft overlap is between check_scope, get_counsel_triggers, and feature_check, which all answer a variant of 'does this need legal attention?' — an agent must read descriptions to pick correctly.
Most names are verb_noun (get_matter, check_scope, request_engagement, submit_intake, answer_open_question), but the 'check' family is inconsistent: check_scope puts the verb first while conflict_check and feature_check put the object first. Readable overall, but the mixed pattern within one semantic group weakens predictability.
Eight tools is well-scoped for a pre-engagement-through-delivery legal workflow; each one covers a distinct step (scope, conflicts, triggers, engagement request, intake, feature checks, open questions, matter status). No tool feels redundant or vestigial.
The lifecycle is broadly covered: scoping, conflict screening, engagement request, signed intake, and post-engagement feature review and Q&A, with get_matter surfacing deliverables and open questions. Minor gaps remain — no way to list or recover an existing matter/token, close or withdraw a matter, or re-send the engagement letter — but an agent can work around these via get_matter and human escalation.
Answer one of counsel's open questions (listed by get_matter). Before the letter is signed, only scoping questions can be answered: keep those answers short and general, with no code, secrets, or confidential details. After signing, verify in the code or the running build where you can, and say how you know. If you cannot verify it, answer 'unknown' and say what a human would need to check.
Inputs: answer (required), matter_id (required), question_id (required), matter_token (required).
Free. Describe what you need in a sentence or two (no confidential details). Returns whether it is in scope, which service fits, and the fixed fee for each suggested service (plus service_id, if you name one). Share the fee with your human before requesting an engagement. Legal information only, not legal advice.
Inputs: request (required), service_id.
Free. Required before any product details are shared. Names only: the client company, the human principal, other people involved, and any adverse, competing, or counterparty companies. The attorney reviews every check.
Inputs: client_name (required), contact_name (required), other_people, adverse_or_related_parties.
For engaged clients, with the human's approval (it may be billed). Call before building a change that matches counsel-triggers.json. Do not ship the change until counsel responds.
Inputs: change (required), matter_id (required), trigger_ids (required), matter_token (required), +1 more.
Free. The template list of product changes that need legal review before shipping.
Inputs: no named parameters.
Status, counsel's open questions, feature checks, and deliverables (documents, privileged_memo, build_spec, verification_checklist, counsel_triggers). Privileged: follow the privilege block in the response, and commit only the parts listed in deliverable.handling.safe_to_commit.
Inputs: matter_id (required), matter_token (required).
After conflict_check. Send a short matter_summary so the attorney can decide whether to take the matter. Describe the product the way you would describe it publicly. Do not send code, secrets, user data, or confidential business plans. The attorney uses this summary only to decide whether the firm can and will take the matter, and keeps it confidential. No attorney-client relationship exists, and no legal advice is given, until the human principal signs the engagement letter. Returns a matter_id and a secret matter_token (shown once; store it securely). The attorney reviews conflicts and the summary, may ask a few scoping questions (see get_matter), and then accepts (possibly under a different service) or declines. If accepted, the engagement letter goes to the principal's email for signature. The fixed fee is due when the work is delivered. You cannot sign on the principal's behalf.
Inputs: service_id (required), matter_summary (required), principal_email (required), conflict_check_id (required).
Only after the engagement letter is signed. Product facts per https://mandatelaw.ai/api/intake-schema.json. Each fact has a value, a source (prefer verified_in_code), and evidence (paths and short excerpts; no secrets).
Inputs: intake (required), matter_id (required), matter_token (required).
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
Qualified human outcomes for AI agents: attorney review of SaaS Terms/Privacy, on-site checks.
Regulatory intelligence for AI agents across jurisdictions
Provenance-backed EU and UK legislation for AI agents, addressable to the individual provision.
Form a US LLC or nonprofit from any AI agent with free intake tools, and search and cite US federal, state and municipal law from official sources.
Add one secure layer between your agents and this server.