- Home
- Resources
- Integrations
- Descrybe Legal Engine
Claude Descrybe Legal Engine connectorWhat Claude can do in your Descrybe Legal Engine account.
The Claude Descrybe Legal Engine connector exposes 13 tools, all 13 of them reads. 0 write tools, 0 undocumented. Here: how Claude searches U.S. primary law with it, what it sends to Descrybe, what you still have to check, and who can switch it off.
Verified Trustpilot reviews · AI, automation & growth agency
Why a litigation team would plug Descrybe into Claude
You ask the legal question the way you would ask a colleague, and Claude does the digging. It decides which research it needs, calls the Descrybe tools for cases, laws, treatment and passages, then answers from what those tools brought back. You stay in one chat instead of copying citations between tabs.
Start from an issue, not a keyword. An associate describes a retaliation fact pattern. search_cases_by_concept finds cases on that legal concept even when the opinions use other words, and search_laws_and_rules brings back the statutes and regulations that govern it.
Clean up a messy brief. Opposing counsel's brief cites a dozen cases in shorthand. extract_case_references pulls them out of the pasted text, find_case_from_reference resolves each one, and check_case_status gives a quick signal on how later courts treated them.
Make sure a quote is real. Before a filing goes out, verify_quote checks whether the quoted language appears in the case and points to where, and get_case_pdf fetches the opinion so you can read it in full.
Now the limits. Descrybe covers U.S. primary law, not other jurisdictions. It finds and checks sources, and Descrybe itself frames the results as material for your review. It also needs a Descrybe subscription of its own. And nothing runs by itself: no tool wakes up when a case you cited gets overturned. That kind of background watch is an automation job, a different trade; our Integrations hub gathers that side.
Five words before you start
The vocabulary you will meet while connecting Descrybe.
- Connector
- The link you set up once between Claude and an account you already have, so Claude can use it while it answers you.
- Tool
- One named action a connector opens to Claude. Claude picks the ones it needs by itself, and the directory lists them by name.
- Authorization
- The sign-in screen of the service itself, where you give Claude the access it will use. Granted once per person, and you can revoke it.
- Approval
- The confirmation Claude waits for before finishing something that changes your account, shown in the chat at the moment it matters.
- MCP
- The shared standard behind connectors: it is what lets an assistant like Claude talk to an outside service such as Descrybe.
Plug Descrybe Legal Engine into Claude in three steps
- 01
Find Descrybe in Claude
In Claude's settings, open Customize, then Connectors, and look for Descrybe Legal Engine. On a Team or Enterprise workspace, an Owner or Primary Owner has to enable the connector before each member can sign in.
- 02
Start the connection
Click Connect on its row, then sign in to Descrybe in the window Descrybe opens. If the link breaks one day, use Disconnect and connect again; you can also withdraw access from your Descrybe account.
- 03
Read the authorization screen
Read the sign-in screen before confirming. It belongs to Descrybe, not to Claude, and it is what sets the scope of the access. Some services show broader permissions there than Claude uses day to day.
The 13 tools, grouped by what they do
Descrybe Legal Engine gives Claude 13 tools: 13 that read your account, 0 that change something in it.
All thirteen read. Names stay exactly as Claude displays them, in English.
- 13 read
Tools index
What Claude reads (13)
13 toolsThirteen research tools that look up legal sources without changing anything in your account.
analyze_legal_question
Helps Claude judge whether your question has enough to start research, and ask a few targeted questions when the basics are missing.
search_cases_by_concept
Finds cases by legal issue, rule, concept or fact pattern. Authority signals weigh in, so stronger cases surface even when the wording differs from yours.
search_case_text
Searches opinions for the precise words or phrase you give, rather than the idea behind them.
find_case_from_reference
Turns a citation, case name, docket number, short cite or garbled reference into the right case, or a short list of candidates.
extract_case_references
Reads legal text you paste and lists the cases it cites, grouping repeats so you see which authorities are really in play in that text.
get_case_details
Gathers the caption, court, date, available summaries, opinion inventory and treatment overview of one case in a single answer, so you do not have to open four tabs for it.
get_case_pdf
Retrieves the opinion PDF itself, so the underlying source is easy to inspect, print or share with the team. You get the document, not a paraphrase of it.
get_case_passages
Pulls the passages of a known case that bear on your question, so Claude reasons from the language that matters instead of the whole opinion.
get_case_summary
Returns a short, research-ready summary and analysis of a case you already identified, before Claude digs into the opinion itself and starts reasoning from it.
search_laws_and_rules
Looks up statutes, regulations and constitutional provisions by topic, phrase or citation, and brings back the relevant source language rather than a description of it.
check_case_status
Shows how later cases appear to treat an authority, with a quick positive, negative, cautious or neutral signal.
find_cases_that_cite
Lists newer cases that cite the one you are looking at, which is how you trace later treatment and follow-on authority.
verify_quote
Tells you whether a quoted line actually appears in a known case, and points to the spot where it matches.
What Claude asks you before it acts
By default, Claude stops and asks for your go-ahead before each action it takes on an account for you. The request shows up in the conversation, right when it matters.
On Team and Enterprise, workspace owners decide whether a member can let some actions through without being asked again. They can also cap what a connector may do for the whole organization, for example keep reading open and close writing, and that setting applies to everyone. Claude works with your rights and nothing more: what your Descrybe account cannot reach, Claude cannot reach either. The official per-tool label (read-only versus write and delete) only appears in a connected account's settings.
Which plans it works on
Across the 819 sheets of the official directory, 0 shows plan availability. The connector-by-connector answer is not published anywhere: that is a real gap in the catalog.
The general rule is published: remote connectors are open to all users on Claude, Cowork, Claude Desktop and mobile. On Team and Enterprise, an Owner or Primary Owner opens the connector for the organization before each member can connect. Descrybe's own subscription is a separate matter, covered in the limits below. For the up-to-date state, the connector's sheet in the official directory is the place to check.
Where this connector stops
A connector is not an automation. Claude calls these tools while it answers you: nothing starts when a new opinion lands or a cited case is reversed.
Only Descrybe documents this connector; no Claude help page covers it. A tool list that shows only reads is an observed floor, not a guarantee, because an administrator can open actions that appear on no public sheet. The partner badge is not a security audit, and Anthropic states on every sheet that it does not pick the tools a publisher exposes or guarantee how they behave. Connect what comes from a publisher you trust. Every directory connector has its own page with us, such as the Claude affinity connector.
Need help connecting Descrybe Legal Engine to Claude?
A person reads every message.