Integration details
Description
Vasara connects ChatGPT to Lithuania's primary legal sources: national legislation, EU regulations and directives, and case law from the Constitutional Court, Supreme Court, Supreme Administrative Court, the Court of Justice of the EU, and the European Court of Human Rights. Use it to look up a specific court decision by case number, search case law and legislation by topic, pull relevant passages from long legal documents, or find guidance from state authorities and municipalities — with sources ChatGPT can cite directly in its answers. Plugin searches and retrieves legal sources, doesn't create, edit, or submit anything. Requires a Vasara account.
- Integration type
- Plugin
- Verification status
- Not applicable
- Platform
- ChatGPT
- Primary Subcategory
- Legal Research Engines
- Secondary Subcategories
- None listed
- Brand
- Vasara
- Access
- Account required
- First tracked
- 2026-08-20
- Tool count
- 24
- Geography
- US
The Primary Subcategory used for this profile’s headline score.
Other Subcategories where the Integration is listed.
ChatGPT Plugin Discovery Score
ChatGPT Plugin discovery is coming soon
ChatGPT can surface a Plugin when it matches a user's request.Your Plugin Discovery Score measures how often yours appears.
No spam. Unsubscribe any time.
What discovery looks like
Competing in ChatGPT Legal Research Engines
View Category24 tools agents can invoke
Run aggregations over insight grid cells: count, sum, average, min, max, count_by_value, count_by_flag. Pass gridId from list-project-insight-grids on MCP; insight-grid assistants may omit it when pinned. CITING SOURCES: In your answer, ALWAYS link every source you rely on whenever a URL is available. When a result item includes a `sourceLink` field, cite it as a markdown link using the exact Vasara URL, e.g. `[case number or law title](sourceLink)`. For organization website results, link the exact external URL returned. Never present a legal source as plain text when a link can be included, and never invent or alter URLs. ## Vasara source links - Legal-corpus `sourceLink` values are authenticated Vasara URLs (`/mcp/chunk/<token>` or `/mcp/document/<token>`). Copy them verbatim into markdown links: `[descriptive label](sourceLink)`. - Project, project-document, and insight-grid `sourceLink` values are authenticated Vasara URLs (`/mcp/project/<token>`, `/mcp/project-document/<token>`, `/mcp/insight-grid/<token>`). Copy them verbatim; they open the existing project UI after login. - Prefer `sourceLink` / `citationMarkdown` over `citationToken` or inventing `/project/...` paths with raw UUIDs. - Organization website search results still use the exact external `https://` URLs returned by the tool. Do not rewrite those into Vasara links.
calculate-insight-grid
Check for additional tools whenever your task might benefit from specialized capabilities - even if existing tools could work as a fallback.
get_more_tools
Fetch full text of a court judgment when the user gives an exact case number (document title match). Use this to verify the validity, relevance, or current status of specific court cases mentioned in a document or prompt. Expensive—use only when full text is required. CITING SOURCES: In your answer, ALWAYS link every source you rely on whenever a URL is available. When a result item includes a `sourceLink` field, cite it as a markdown link using the exact Vasara URL, e.g. `[case number or law title](sourceLink)`. For organization website results, link the exact external URL returned. Never present a legal source as plain text when a link can be included, and never invent or alter URLs. ## Vasara source links - Legal-corpus `sourceLink` values are authenticated Vasara URLs (`/mcp/chunk/<token>` or `/mcp/document/<token>`). Copy them verbatim into markdown links: `[descriptive label](sourceLink)`. - Project, project-document, and insight-grid `sourceLink` values are authenticated Vasara URLs (`/mcp/project/<token>`, `/mcp/project-document/<token>`, `/mcp/insight-grid/<token>`). Copy them verbatim; they open the existing project UI after login. - Prefer `sourceLink` / `citationMarkdown` over `citationToken` or inventing `/project/...` paths with raw UUIDs. - Organization website search results still use the exact external `https://` URLs returned by the tool. Do not rewrite those into Vasara links. Before legal research, read the `getLegalResearchInstructions` tool description for the full protocol (tool order, parallel batching, persistence, citations).
get-court-case-by-case-number
Return insight grid metadata: columns, rows (document names), and cell status counts. Does not include full cell text — call queryInsightGridCells for values. Pass gridId (opaque token from list-project-insight-grids) on MCP; insight-grid assistants may omit it when a grid is already pinned. When sourceLink is present (MCP), cite the grid with that URL. CITING SOURCES: In your answer, ALWAYS link every source you rely on whenever a URL is available. When a result item includes a `sourceLink` field, cite it as a markdown link using the exact Vasara URL, e.g. `[case number or law title](sourceLink)`. For organization website results, link the exact external URL returned. Never present a legal source as plain text when a link can be included, and never invent or alter URLs. ## Vasara source links - Legal-corpus `sourceLink` values are authenticated Vasara URLs (`/mcp/chunk/<token>` or `/mcp/document/<token>`). Copy them verbatim into markdown links: `[descriptive label](sourceLink)`. - Project, project-document, and insight-grid `sourceLink` values are authenticated Vasara URLs (`/mcp/project/<token>`, `/mcp/project-document/<token>`, `/mcp/insight-grid/<token>`). Copy them verbatim; they open the existing project UI after login. - Prefer `sourceLink` / `citationMarkdown` over `citationToken` or inventing `/project/...` paths with raw UUIDs. - Organization website search results still use the exact external `https://` URLs returned by the tool. Do not rewrite those into Vasara links.
get-insight-grid-snapshot
Fetch the full converted text content of a project document by projectDocumentId (opaque token from list/search — not a project id). No projectId arg required. When sourceLink is present (MCP), prefer that URL for citations. Returns deleted=true when the document has been removed. CITING SOURCES: In your answer, ALWAYS link every source you rely on whenever a URL is available. When a result item includes a `sourceLink` field, cite it as a markdown link using the exact Vasara URL, e.g. `[case number or law title](sourceLink)`. For organization website results, link the exact external URL returned. Never present a legal source as plain text when a link can be included, and never invent or alter URLs. ## Vasara source links - Legal-corpus `sourceLink` values are authenticated Vasara URLs (`/mcp/chunk/<token>` or `/mcp/document/<token>`). Copy them verbatim into markdown links: `[descriptive label](sourceLink)`. - Project, project-document, and insight-grid `sourceLink` values are authenticated Vasara URLs (`/mcp/project/<token>`, `/mcp/project-document/<token>`, `/mcp/insight-grid/<token>`). Copy them verbatim; they open the existing project UI after login. - Prefer `sourceLink` / `citationMarkdown` over `citationToken` or inventing `/project/...` paths with raw UUIDs. - Organization website search results still use the exact external `https://` URLs returned by the tool. Do not rewrite those into Vasara links.
get-project-document-content
List all documents in a project. Pass projectId (opaque token from list-projects) on MCP; in-app assistants may omit it when a project is already pinned. Returns projectDocumentId tokens for get-project-document-content — do not use a project id there. When sourceLink is present (MCP), prefer that URL for citations. CITING SOURCES: In your answer, ALWAYS link every source you rely on whenever a URL is available. When a result item includes a `sourceLink` field, cite it as a markdown link using the exact Vasara URL, e.g. `[case number or law title](sourceLink)`. For organization website results, link the exact external URL returned. Never present a legal source as plain text when a link can be included, and never invent or alter URLs. ## Vasara source links - Legal-corpus `sourceLink` values are authenticated Vasara URLs (`/mcp/chunk/<token>` or `/mcp/document/<token>`). Copy them verbatim into markdown links: `[descriptive label](sourceLink)`. - Project, project-document, and insight-grid `sourceLink` values are authenticated Vasara URLs (`/mcp/project/<token>`, `/mcp/project-document/<token>`, `/mcp/insight-grid/<token>`). Copy them verbatim; they open the existing project UI after login. - Prefer `sourceLink` / `citationMarkdown` over `citationToken` or inventing `/project/...` paths with raw UUIDs. - Organization website search results still use the exact external `https://` URLs returned by the tool. Do not rewrite those into Vasara links.
get-project-documents-list
Vasara legal research protocol. Read this description before using any search tool — no need to call this tool. ## Parallel tool calls (CRITICAL) Issue all independent searches in one parallel batch — same or different tools in a single step. Never call a tool, wait for the result, then call another when you already know both searches are needed and their inputs do not depend on each other. ## Source Strategy 1. **MASTER SEARCH PROTOCOL (CRITICAL — MUST FOLLOW FOR EVERY LEGAL QUESTION):** **STEP 1 — Initial Search:** ALWAYS call `search-laws` first. (Exception: If you exclusively verify or extract specific court cases by number, call `search-case-law` or `get-court-case-by-case-number` without requiring `search-laws` first.) If specific document titles are referenced, ALSO call `search-chunks-from-document-by-title` in parallel. If the question involves disputes, court decisions, complex practical scenarios, or rights/obligations in practice, ALSO call `search-case-law` in parallel for Lithuanian judicial interpretation. **SPECIFIC-COURT EXCEPTION:** If the user seeks practice from a named court ("LAT", "LVAT", "LApT", appellate courts), do NOT use `search-case-law`. USE `search-specific-court-case-law` with `court` exactly `"LAT"`, `"LVAT"`, or `"LApT"`. **ECHR / CONVENTION:** If hints mark ECHR relevance, or questions cover ECHR/EŽTT Strasbourg HUDOC or Convention standards, ALSO call `search-echr-judgments` — `search-case-law` is not sufficient for ECHR-only needs. **STEP 2 — EVALUATE:** After EACH search wave, ask whether you found an explicit rule answering the question. Definitions without permission/prohibition ARE NOT ENOUGH ("definition trap"). KEEP SEARCHING when only context was found. **STEP 3 — Tool switching:** Never call `search-laws` twice in a row without a different tool in between when results are inadequate. Alternate with `search-legal-acts`, `search-case-law`, `search-specific-court-case-law`, `search-echr-judgments`, `search-municipalities-documents`, `search-organization-documents`. **STEP 4 — Persistence:** Attempt up to **4 substantive search iterations** with varied keywords and tools before concluding absence of sources. **STEP 5 — No early quitting:** Delivering shallow "interpretation" after only one unsuccessful search is a failure. **STEP 6 — "Undefined" claims require proof of absence:** NEVER claim "the law does not define X" based on your internal knowledge or a limited search. If a term is not defined in a specific context (e.g., "in the context of residential lease"), you MUST broaden your search by removing contextual keywords and searching for the general definition of the term (e.g., searching for "einamasis remontas" alone without "nuoma"). You MUST conduct comprehensive searches across all relevant domains (including general acts, e.g., "Statybos įstatymas" for construction/repair, "Civilinis kodeksas" for general terms) using `search-laws` and `search-legal-acts` before concluding a definition does not exist. 2. If nothing relevant exists after exhaustive search (per above), explicitly state that the corpus did not yield an answer. DO NOT invent or infer an answer from your general knowledge. NEVER claim 'in practice it means...' (e.g. 'teismų praktikoje... paprastai apima...') without citing specific cases that establish those practices. 3. Prefer efficient search tools. Use `get-court-case-by-case-number` only when explicit court-case retrieval by case number is required. 4. **Case-law date windows:** For `search-case-law` / `search-specific-court-case-law`, start with `dateFrom` ≈ three years ago. If empty or insufficient: retry with six-to-three-year window; if still empty: final pass with upper bound six years ago. 5. ECHR mandates `search-echr-judgments` when Convention jurisprudence matters. 6. **Parallelize tool calls aggressively (INCLUDING THE SAME TOOL):** You can and SHOULD call the *same* tool multiple times in parallel during the same step if you need to search multiple distinct angles, courts, or date windows. For example, you can call `search-specific-court-case-law` 3 times in parallel in a single run (one for LAT, one for LVAT, one for LApT) or with different queries. Do NOT call a tool once, wait for the result, and then call it again if you already know you need to run multiple searches. Parallelize them in a single step whenever inputs do not depend on each other. 7. **Query splitting:** Do not combine multiple distinct concepts into one long query string (e.g., 'gyvenamųjų patalpų nuomos sutarties esminės sąlygos nuomininko rizikos užstatas sutarties nutraukimas'). Instead, split complex queries into multiple focused, single-concept queries. 8. **Synthesize Laws and Case Law:** When formulating your response, if a statutory rule has been interpreted or applied in case law, you MUST cite BOTH the statutory law and ALL the relevant court cases together. Do not provide an answer based only on laws if you also retrieved case law that confirms, applies, or explains those laws. If multiple cases say the same thing, CITE ALL OF THEM. **CRITICAL:** If the user specifically asks for court practice (e.g., 'teismų praktika', 'LAT praktika'), you MUST cite court cases. Answering a question about court practice using only statutory laws (like the Civil Code) is a FATAL ERROR. 9. **vectorSearchQuery is a single string (never an array):** Every search tool requires `vectorSearchQuery` to be one non-empty Lithuanian query string. NEVER pass an array (and never `[]`) for `vectorSearchQuery`. Do not call a search tool until that one query string is ready. 10. **Batched queries (preferred):** To run several alternative queries with identical filters in a single call, keep one in `vectorSearchQuery` and put the rest (1–7 more) in the optional `additionalVectorSearchQueries` array; they are embedded and executed in parallel, round-robin interleaved, and deduped. Each distinct query adds up to 8 snippets (maximum 24 total). Each returned snippet includes `matchedQueries` listing which query string(s) found it — use that to judge which search angle produced the evidence; multiple matches indicate consensus. Omit `additionalVectorSearchQueries` entirely when you only have one query — never send it as an empty array. 11. If different filters (e.g. different `court`, `dateFrom`, `documentId`) are needed for the same hypothesis, issue parallel duplicate calls — only use `additionalVectorSearchQueries` when filters are identical. 12. When early tries return zero hits, widen keywords before giving up. 13. Retry failed tool calls once with unchanged args; thereafter report incapacity. 14. **No duplicate searches:** The runtime hard-deduplicates tool calls within a single run — issuing the same tool with the same input, or any call whose entire result was already returned by an earlier call in this run, will return a `DUPLICATE SEARCH SKIPPED` / `All matched chunks were already returned` message and zero new content. Treat that signal as a hard pivot cue: switch the tool, the hypothesis, the query angle, the filters, or the date window — never simply re-issue the search. 15. When secondary results cite primary statutes (CK, DK, BK, …), fetch primary text via `search-chunks-from-document-by-title` BEFORE citing operative rules. 16. Never cite a statutory rule sourced only through case excerpts without confirming the statute text. 17. If statutes cannot be confirmed, omit the rule from conclusions and disclose verification failure. 18. **Complete parameters:** Respect every mandatory field in schemas. ## Illustrative Drill Patterns 1. Case verification: Combine `get-court-case-by-case-number`, `search-specific-court-case-law`, then answer with markdown citation links. 2. Longitudinal XYZ doctrine: Exhaust three date windows on `search-case-law` before concluding no precedent. 3. PHEV / EV lanes: Alternate `search-laws`, `search-legal-acts`, municipal lookup until an operative traffic rule emerges or exhaustion is justified. ## Tool selection - Start with `search-laws` for most legal questions. - Use `search-legal-acts` for specific statutes and regulations. - Use `search-legal-sources` when the document type is unclear or the query spans several source kinds. - Use `search-case-law` for court practice and judicial interpretation. - Use `search-specific-court-case-law` with `court` set to `"LAT"`, `"LVAT"`, or `"LApT"` when practice from a named court is needed. - Use `search-echr-judgments` for ECHR / Convention jurisprudence. - Use `search-municipalities-documents` for municipal regulations. - Use `search-organization-documents` / `search-organization-websites` for organization-specific material. - Use `search-chunks-from-document-by-title` or `search-chunks-from-document-by-id` to search inside a known document. - Use `search-chunks-from-court-case-by-number` or `get-court-case-by-case-number` when a specific court case number is given. ## Query rules - Vector search queries MUST be in Lithuanian. Expand abbreviations and add alternative terms in brackets. - Batch alternative queries via `additionalVectorSearchQueries` rather than repeating tool calls with identical inputs. - For case law, start with `dateFrom` ≈ three years ago; widen the window if results are insufficient. ## Source links in answers - **Always link your sources in the final answer whenever a URL is available.** Do not cite legal sources as plain text only if a link can be included. - When a snippet or court-case result includes `sourceLink`, cite it as a markdown link: `[descriptive label](sourceLink)`. Use the exact URL from the tool result — never invent or modify it. ## Vasara source links - Legal-corpus `sourceLink` values are authenticated Vasara URLs (`/mcp/chunk/<token>` or `/mcp/document/<token>`). Copy them verbatim into markdown links: `[descriptive label](sourceLink)`. - Project, project-document, and insight-grid `sourceLink` values are authenticated Vasara URLs (`/mcp/project/<token>`, `/mcp/project-document/<token>`, `/mcp/insight-grid/<token>`). Copy them verbatim; they open the existing project UI after login. - Prefer `sourceLink` / `citationMarkdown` over `citationToken` or inventing `/project/...` paths with raw UUIDs. - Organization website search results still use the exact external `https://` URLs returned by the tool. Do not rewrite those into Vasara links. - If multiple snippets support the same point, include a link for each distinct source where `sourceLink` (or an organization URL) is available. - Snippets may also include `citationToken` for internal corpus references (`[label](/?chunk=<citationToken>)`). Use that only when no `sourceLink` or organization URL exists. - Use the exact `citationToken` from tool results — never invent values.
get-legal-research-instructions
List all insight grids in a project with row and column counts. Pass projectId (opaque token from list-projects) on MCP; in-app assistants may omit it when a project is already pinned. Returned grid ids are opaque tokens for get-insight-grid-snapshot / query / calculate. When sourceLink is present (MCP), cite grids with that URL. CITING SOURCES: In your answer, ALWAYS link every source you rely on whenever a URL is available. When a result item includes a `sourceLink` field, cite it as a markdown link using the exact Vasara URL, e.g. `[case number or law title](sourceLink)`. For organization website results, link the exact external URL returned. Never present a legal source as plain text when a link can be included, and never invent or alter URLs. ## Vasara source links - Legal-corpus `sourceLink` values are authenticated Vasara URLs (`/mcp/chunk/<token>` or `/mcp/document/<token>`). Copy them verbatim into markdown links: `[descriptive label](sourceLink)`. - Project, project-document, and insight-grid `sourceLink` values are authenticated Vasara URLs (`/mcp/project/<token>`, `/mcp/project-document/<token>`, `/mcp/insight-grid/<token>`). Copy them verbatim; they open the existing project UI after login. - Prefer `sourceLink` / `citationMarkdown` over `citationToken` or inventing `/project/...` paths with raw UUIDs. - Organization website search results still use the exact external `https://` URLs returned by the tool. Do not rewrite those into Vasara links.
list-project-insight-grids
List accessible projects and open the interactive project picker UI (MCP Apps). Call this (or select-project-or-grid with mode=project) when the user must choose a project — do not paste project names into chat for them to type back. Project ids are opaque user-scoped tokens — pass them as projectId to get-project-documents-list, search-project-documents, or list-project-insight-grids. After they pick, continue with those tools using the token; do not re-list names. CITING SOURCES: In your answer, ALWAYS link every source you rely on whenever a URL is available. When a result item includes a `sourceLink` field, cite it as a markdown link using the exact Vasara URL, e.g. `[case number or law title](sourceLink)`. For organization website results, link the exact external URL returned. Never present a legal source as plain text when a link can be included, and never invent or alter URLs. ## Vasara source links - Legal-corpus `sourceLink` values are authenticated Vasara URLs (`/mcp/chunk/<token>` or `/mcp/document/<token>`). Copy them verbatim into markdown links: `[descriptive label](sourceLink)`. - Project, project-document, and insight-grid `sourceLink` values are authenticated Vasara URLs (`/mcp/project/<token>`, `/mcp/project-document/<token>`, `/mcp/insight-grid/<token>`). Copy them verbatim; they open the existing project UI after login. - Prefer `sourceLink` / `citationMarkdown` over `citationToken` or inventing `/project/...` paths with raw UUIDs. - Organization website search results still use the exact external `https://` URLs returned by the tool. Do not rewrite those into Vasara links.
list-projects
Query insight grid cell values with optional filters by column/row IDs or indices, status, or tag flag. Pass gridId from list-project-insight-grids on MCP; insight-grid assistants may omit it when pinned. CITING SOURCES: In your answer, ALWAYS link every source you rely on whenever a URL is available. When a result item includes a `sourceLink` field, cite it as a markdown link using the exact Vasara URL, e.g. `[case number or law title](sourceLink)`. For organization website results, link the exact external URL returned. Never present a legal source as plain text when a link can be included, and never invent or alter URLs. ## Vasara source links - Legal-corpus `sourceLink` values are authenticated Vasara URLs (`/mcp/chunk/<token>` or `/mcp/document/<token>`). Copy them verbatim into markdown links: `[descriptive label](sourceLink)`. - Project, project-document, and insight-grid `sourceLink` values are authenticated Vasara URLs (`/mcp/project/<token>`, `/mcp/project-document/<token>`, `/mcp/insight-grid/<token>`). Copy them verbatim; they open the existing project UI after login. - Prefer `sourceLink` / `citationMarkdown` over `citationToken` or inventing `/project/...` paths with raw UUIDs. - Organization website search results still use the exact external `https://` URLs returned by the tool. Do not rewrite those into Vasara links.
query-insight-grid-cells
Searches only ECHR (European Court of Human Rights / EŽTT) judgments. Use for Convention rights, Strasbourg standards, or HUDOC-style questions—not for Lithuanian domestic courts only. To batch several alternative queries in one call, keep one in vectorSearchQuery and put the rest in additionalVectorSearchQueries; they are searched in parallel, round-robin interleaved, deduped, and each snippet includes matchedQueries. Each distinct query adds up to 8 snippets (maximum 24 total). CITING SOURCES: In your answer, ALWAYS link every source you rely on whenever a URL is available. When a result item includes a `sourceLink` field, cite it as a markdown link using the exact Vasara URL, e.g. `[case number or law title](sourceLink)`. For organization website results, link the exact external URL returned. Never present a legal source as plain text when a link can be included, and never invent or alter URLs. ## Vasara source links - Legal-corpus `sourceLink` values are authenticated Vasara URLs (`/mcp/chunk/<token>` or `/mcp/document/<token>`). Copy them verbatim into markdown links: `[descriptive label](sourceLink)`. - Project, project-document, and insight-grid `sourceLink` values are authenticated Vasara URLs (`/mcp/project/<token>`, `/mcp/project-document/<token>`, `/mcp/insight-grid/<token>`). Copy them verbatim; they open the existing project UI after login. - Prefer `sourceLink` / `citationMarkdown` over `citationToken` or inventing `/project/...` paths with raw UUIDs. - Organization website search results still use the exact external `https://` URLs returned by the tool. Do not rewrite those into Vasara links. Before legal research, read the `getLegalResearchInstructions` tool description for the full protocol (tool order, parallel batching, persistence, citations).
search-echr-judgments
Searches for case law sources from courts. Use this tool when you need case law for a given topic, or to verify the relevance, validity, and current status of specific court cases (e.g. to check if a case has been overturned, modified, or if new practice has been formed). CRITICAL: DO NOT use this tool if the user asks for practice from a specific court like LAT (Lietuvos Aukščiausiasis Teismas), LVAT (Lietuvos vyriausiasis administracinis teismas), or LApT (Lietuvos apeliacinis teismas). For those specific courts, you MUST use search-specific-court-case-law with court set to "LAT", "LVAT", or "LApT" (not the full court name). Search in three time periods if needed: 1. First call with dateFrom set to 3 years ago. 2. If no results, call again with dateFrom 6 years ago and dateTo 3 years ago. 3. If still no results, call one last time with dateTo 6 years ago (no dateFrom). Do not give up until all three time periods have been tried. The vector search query MUST be in Lithuanian. Expand all abbreviations and acronyms. Add alternative terms in brackets. To batch several alternative queries in one call, keep one in vectorSearchQuery and put the rest in additionalVectorSearchQueries; they are searched in parallel, round-robin interleaved, deduped, and each snippet includes matchedQueries. Each distinct query adds up to 8 snippets (maximum 24 total). CITING SOURCES: In your answer, ALWAYS link every source you rely on whenever a URL is available. When a result item includes a `sourceLink` field, cite it as a markdown link using the exact Vasara URL, e.g. `[case number or law title](sourceLink)`. For organization website results, link the exact external URL returned. Never present a legal source as plain text when a link can be included, and never invent or alter URLs. ## Vasara source links - Legal-corpus `sourceLink` values are authenticated Vasara URLs (`/mcp/chunk/<token>` or `/mcp/document/<token>`). Copy them verbatim into markdown links: `[descriptive label](sourceLink)`. - Project, project-document, and insight-grid `sourceLink` values are authenticated Vasara URLs (`/mcp/project/<token>`, `/mcp/project-document/<token>`, `/mcp/insight-grid/<token>`). Copy them verbatim; they open the existing project UI after login. - Prefer `sourceLink` / `citationMarkdown` over `citationToken` or inventing `/project/...` paths with raw UUIDs. - Organization website search results still use the exact external `https://` URLs returned by the tool. Do not rewrite those into Vasara links. Before legal research, read the `getLegalResearchInstructions` tool description for the full protocol (tool order, parallel batching, persistence, citations).
search-case-law
Find a court judgment document whose title equals the case number, then search inside it. Use this to verify the relevance or find specific quotes within a court case mentioned in a document or prompt. To batch several alternative queries in one call, keep one in vectorSearchQuery and put the rest in additionalVectorSearchQueries; they are searched in parallel, round-robin interleaved, deduped, and each snippet includes matchedQueries. Each distinct query adds up to 8 snippets (maximum 24 total). CITING SOURCES: In your answer, ALWAYS link every source you rely on whenever a URL is available. When a result item includes a `sourceLink` field, cite it as a markdown link using the exact Vasara URL, e.g. `[case number or law title](sourceLink)`. For organization website results, link the exact external URL returned. Never present a legal source as plain text when a link can be included, and never invent or alter URLs. ## Vasara source links - Legal-corpus `sourceLink` values are authenticated Vasara URLs (`/mcp/chunk/<token>` or `/mcp/document/<token>`). Copy them verbatim into markdown links: `[descriptive label](sourceLink)`. - Project, project-document, and insight-grid `sourceLink` values are authenticated Vasara URLs (`/mcp/project/<token>`, `/mcp/project-document/<token>`, `/mcp/insight-grid/<token>`). Copy them verbatim; they open the existing project UI after login. - Prefer `sourceLink` / `citationMarkdown` over `citationToken` or inventing `/project/...` paths with raw UUIDs. - Organization website search results still use the exact external `https://` URLs returned by the tool. Do not rewrite those into Vasara links. Before legal research, read the `getLegalResearchInstructions` tool description for the full protocol (tool order, parallel batching, persistence, citations).
search-chunks-from-court-case-by-number
Vector search restricted to a single legal document (document thread token). To batch several alternative queries in one call, keep one in vectorSearchQuery and put the rest in additionalVectorSearchQueries; they are searched in parallel, round-robin interleaved, deduped, and each snippet includes matchedQueries. Each distinct query adds up to 8 snippets (maximum 24 total). CITING SOURCES: In your answer, ALWAYS link every source you rely on whenever a URL is available. When a result item includes a `sourceLink` field, cite it as a markdown link using the exact Vasara URL, e.g. `[case number or law title](sourceLink)`. For organization website results, link the exact external URL returned. Never present a legal source as plain text when a link can be included, and never invent or alter URLs. ## Vasara source links - Legal-corpus `sourceLink` values are authenticated Vasara URLs (`/mcp/chunk/<token>` or `/mcp/document/<token>`). Copy them verbatim into markdown links: `[descriptive label](sourceLink)`. - Project, project-document, and insight-grid `sourceLink` values are authenticated Vasara URLs (`/mcp/project/<token>`, `/mcp/project-document/<token>`, `/mcp/insight-grid/<token>`). Copy them verbatim; they open the existing project UI after login. - Prefer `sourceLink` / `citationMarkdown` over `citationToken` or inventing `/project/...` paths with raw UUIDs. - Organization website search results still use the exact external `https://` URLs returned by the tool. Do not rewrite those into Vasara links. Before legal research, read the `getLegalResearchInstructions` tool description for the full protocol (tool order, parallel batching, persistence, citations).
search-chunks-from-document-by-id
Resolve a document by title (embedding match), then run a vector search restricted to that document. To batch several alternative queries in one call, keep one in vectorSearchQuery and put the rest in additionalVectorSearchQueries; they are searched in parallel, round-robin interleaved, deduped, and each snippet includes matchedQueries. Each distinct query adds up to 8 snippets (maximum 24 total). CITING SOURCES: In your answer, ALWAYS link every source you rely on whenever a URL is available. When a result item includes a `sourceLink` field, cite it as a markdown link using the exact Vasara URL, e.g. `[case number or law title](sourceLink)`. For organization website results, link the exact external URL returned. Never present a legal source as plain text when a link can be included, and never invent or alter URLs. ## Vasara source links - Legal-corpus `sourceLink` values are authenticated Vasara URLs (`/mcp/chunk/<token>` or `/mcp/document/<token>`). Copy them verbatim into markdown links: `[descriptive label](sourceLink)`. - Project, project-document, and insight-grid `sourceLink` values are authenticated Vasara URLs (`/mcp/project/<token>`, `/mcp/project-document/<token>`, `/mcp/insight-grid/<token>`). Copy them verbatim; they open the existing project UI after login. - Prefer `sourceLink` / `citationMarkdown` over `citationToken` or inventing `/project/...` paths with raw UUIDs. - Organization website search results still use the exact external `https://` URLs returned by the tool. Do not rewrite those into Vasara links. Before legal research, read the `getLegalResearchInstructions` tool description for the full protocol (tool order, parallel batching, persistence, citations).
search-chunks-from-document-by-title
Searches for laws (documents with type 'law'). Use this tool when you specifically need to find information in laws. The vector search query MUST be in Lithuanian. Expand all abbreviations and acronyms. Add alternative terms in brackets. To batch several alternative queries in one call, keep one in vectorSearchQuery and put the rest in additionalVectorSearchQueries; they are searched in parallel, round-robin interleaved, deduped, and each snippet includes matchedQueries. Each distinct query adds up to 8 snippets (maximum 24 total). CITING SOURCES: In your answer, ALWAYS link every source you rely on whenever a URL is available. When a result item includes a `sourceLink` field, cite it as a markdown link using the exact Vasara URL, e.g. `[case number or law title](sourceLink)`. For organization website results, link the exact external URL returned. Never present a legal source as plain text when a link can be included, and never invent or alter URLs. ## Vasara source links - Legal-corpus `sourceLink` values are authenticated Vasara URLs (`/mcp/chunk/<token>` or `/mcp/document/<token>`). Copy them verbatim into markdown links: `[descriptive label](sourceLink)`. - Project, project-document, and insight-grid `sourceLink` values are authenticated Vasara URLs (`/mcp/project/<token>`, `/mcp/project-document/<token>`, `/mcp/insight-grid/<token>`). Copy them verbatim; they open the existing project UI after login. - Prefer `sourceLink` / `citationMarkdown` over `citationToken` or inventing `/project/...` paths with raw UUIDs. - Organization website search results still use the exact external `https://` URLs returned by the tool. Do not rewrite those into Vasara links. Before legal research, read the `getLegalResearchInstructions` tool description for the full protocol (tool order, parallel batching, persistence, citations).
search-laws
Searches for Lithuanian national legal acts from government institutions, ministries, and other state bodies. Use this tool when you specifically need laws and regulations from Lithuania. The vector search query MUST be in Lithuanian. Expand all abbreviations and acronyms. Add alternative terms in brackets. To batch several alternative queries in one call, keep one in vectorSearchQuery and put the rest in additionalVectorSearchQueries; they are searched in parallel, round-robin interleaved, deduped, and each snippet includes matchedQueries. Each distinct query adds up to 8 snippets (maximum 24 total). CITING SOURCES: In your answer, ALWAYS link every source you rely on whenever a URL is available. When a result item includes a `sourceLink` field, cite it as a markdown link using the exact Vasara URL, e.g. `[case number or law title](sourceLink)`. For organization website results, link the exact external URL returned. Never present a legal source as plain text when a link can be included, and never invent or alter URLs. ## Vasara source links - Legal-corpus `sourceLink` values are authenticated Vasara URLs (`/mcp/chunk/<token>` or `/mcp/document/<token>`). Copy them verbatim into markdown links: `[descriptive label](sourceLink)`. - Project, project-document, and insight-grid `sourceLink` values are authenticated Vasara URLs (`/mcp/project/<token>`, `/mcp/project-document/<token>`, `/mcp/insight-grid/<token>`). Copy them verbatim; they open the existing project UI after login. - Prefer `sourceLink` / `citationMarkdown` over `citationToken` or inventing `/project/...` paths with raw UUIDs. - Organization website search results still use the exact external `https://` URLs returned by the tool. Do not rewrite those into Vasara links. Before legal research, read the `getLegalResearchInstructions` tool description for the full protocol (tool order, parallel batching, persistence, citations).
search-legal-acts
Broad search across Lithuanian legal acts, EU law, case law, and municipal regulations when the document type is unclear or the query spans several source kinds. To batch several alternative queries in one call, keep one in vectorSearchQuery and put the rest in additionalVectorSearchQueries; they are searched in parallel, round-robin interleaved, deduped, and each snippet includes matchedQueries. Each distinct query adds up to 8 snippets (maximum 24 total). CITING SOURCES: In your answer, ALWAYS link every source you rely on whenever a URL is available. When a result item includes a `sourceLink` field, cite it as a markdown link using the exact Vasara URL, e.g. `[case number or law title](sourceLink)`. For organization website results, link the exact external URL returned. Never present a legal source as plain text when a link can be included, and never invent or alter URLs. ## Vasara source links - Legal-corpus `sourceLink` values are authenticated Vasara URLs (`/mcp/chunk/<token>` or `/mcp/document/<token>`). Copy them verbatim into markdown links: `[descriptive label](sourceLink)`. - Project, project-document, and insight-grid `sourceLink` values are authenticated Vasara URLs (`/mcp/project/<token>`, `/mcp/project-document/<token>`, `/mcp/insight-grid/<token>`). Copy them verbatim; they open the existing project UI after login. - Prefer `sourceLink` / `citationMarkdown` over `citationToken` or inventing `/project/...` paths with raw UUIDs. - Organization website search results still use the exact external `https://` URLs returned by the tool. Do not rewrite those into Vasara links. Before legal research, read the `getLegalResearchInstructions` tool description for the full protocol (tool order, parallel batching, persistence, citations).
search-legal-sources
Search municipality / savivaldybė institution documents (vector DB). To batch several alternative queries in one call, keep one in vectorSearchQuery and put the rest in additionalVectorSearchQueries; they are searched in parallel, round-robin interleaved, deduped, and each snippet includes matchedQueries. Each distinct query adds up to 8 snippets (maximum 24 total). CITING SOURCES: In your answer, ALWAYS link every source you rely on whenever a URL is available. When a result item includes a `sourceLink` field, cite it as a markdown link using the exact Vasara URL, e.g. `[case number or law title](sourceLink)`. For organization website results, link the exact external URL returned. Never present a legal source as plain text when a link can be included, and never invent or alter URLs. ## Vasara source links - Legal-corpus `sourceLink` values are authenticated Vasara URLs (`/mcp/chunk/<token>` or `/mcp/document/<token>`). Copy them verbatim into markdown links: `[descriptive label](sourceLink)`. - Project, project-document, and insight-grid `sourceLink` values are authenticated Vasara URLs (`/mcp/project/<token>`, `/mcp/project-document/<token>`, `/mcp/insight-grid/<token>`). Copy them verbatim; they open the existing project UI after login. - Prefer `sourceLink` / `citationMarkdown` over `citationToken` or inventing `/project/...` paths with raw UUIDs. - Organization website search results still use the exact external `https://` URLs returned by the tool. Do not rewrite those into Vasara links. Before legal research, read the `getLegalResearchInstructions` tool description for the full protocol (tool order, parallel batching, persistence, citations).
search-municipalities-documents
Search documents published by a specific organization (resolve organization by name, then vector search). To batch several alternative queries in one call, keep one in vectorSearchQuery and put the rest in additionalVectorSearchQueries; they are searched in parallel, round-robin interleaved, deduped, and each snippet includes matchedQueries. Each distinct query adds up to 8 snippets (maximum 24 total). CITING SOURCES: In your answer, ALWAYS link every source you rely on whenever a URL is available. When a result item includes a `sourceLink` field, cite it as a markdown link using the exact Vasara URL, e.g. `[case number or law title](sourceLink)`. For organization website results, link the exact external URL returned. Never present a legal source as plain text when a link can be included, and never invent or alter URLs. ## Vasara source links - Legal-corpus `sourceLink` values are authenticated Vasara URLs (`/mcp/chunk/<token>` or `/mcp/document/<token>`). Copy them verbatim into markdown links: `[descriptive label](sourceLink)`. - Project, project-document, and insight-grid `sourceLink` values are authenticated Vasara URLs (`/mcp/project/<token>`, `/mcp/project-document/<token>`, `/mcp/insight-grid/<token>`). Copy them verbatim; they open the existing project UI after login. - Prefer `sourceLink` / `citationMarkdown` over `citationToken` or inventing `/project/...` paths with raw UUIDs. - Organization website search results still use the exact external `https://` URLs returned by the tool. Do not rewrite those into Vasara links. Before legal research, read the `getLegalResearchInstructions` tool description for the full protocol (tool order, parallel batching, persistence, citations).
search-organization-documents
Search the public websites of organizations recorded in the `organization` table using web-search. The search is restricted to the hostnames of the organizations' `url` field — the top organizations (by rank) with a non-empty website are searched. Cite each result as a markdown link with a meaningful label: `[<result.name>](result.url)` — use the returned `name` field as the link text (trim to ≤ 70 chars if needed). Never cite as a bare number like `[1](url)`. Web results use external `https://` links, not relative `/?chunk=` corpus citations. CITING SOURCES: In your answer, ALWAYS link every source you rely on whenever a URL is available. When a result item includes a `sourceLink` field, cite it as a markdown link using the exact Vasara URL, e.g. `[case number or law title](sourceLink)`. For organization website results, link the exact external URL returned. Never present a legal source as plain text when a link can be included, and never invent or alter URLs. ## Vasara source links - Legal-corpus `sourceLink` values are authenticated Vasara URLs (`/mcp/chunk/<token>` or `/mcp/document/<token>`). Copy them verbatim into markdown links: `[descriptive label](sourceLink)`. - Project, project-document, and insight-grid `sourceLink` values are authenticated Vasara URLs (`/mcp/project/<token>`, `/mcp/project-document/<token>`, `/mcp/insight-grid/<token>`). Copy them verbatim; they open the existing project UI after login. - Prefer `sourceLink` / `citationMarkdown` over `citationToken` or inventing `/project/...` paths with raw UUIDs. - Organization website search results still use the exact external `https://` URLs returned by the tool. Do not rewrite those into Vasara links. Before legal research, read the `getLegalResearchInstructions` tool description for the full protocol (tool order, parallel batching, persistence, citations).
search-organization-websites
Semantic search over indexed documents in a project. Pass projectId (opaque token from list-projects) on MCP; in-app assistants may omit it when a project is already pinned. projectDocumentId values are opaque tokens for get-project-document-content. When sourceLink is present (MCP), cite hits with that URL. CITING SOURCES: In your answer, ALWAYS link every source you rely on whenever a URL is available. When a result item includes a `sourceLink` field, cite it as a markdown link using the exact Vasara URL, e.g. `[case number or law title](sourceLink)`. For organization website results, link the exact external URL returned. Never present a legal source as plain text when a link can be included, and never invent or alter URLs. ## Vasara source links - Legal-corpus `sourceLink` values are authenticated Vasara URLs (`/mcp/chunk/<token>` or `/mcp/document/<token>`). Copy them verbatim into markdown links: `[descriptive label](sourceLink)`. - Project, project-document, and insight-grid `sourceLink` values are authenticated Vasara URLs (`/mcp/project/<token>`, `/mcp/project-document/<token>`, `/mcp/insight-grid/<token>`). Copy them verbatim; they open the existing project UI after login. - Prefer `sourceLink` / `citationMarkdown` over `citationToken` or inventing `/project/...` paths with raw UUIDs. - Organization website search results still use the exact external `https://` URLs returned by the tool. Do not rewrite those into Vasara links.
search-project-documents
Searches case law from exactly one Lithuanian high court. Use when the user asks for practice from that court specifically, or when narrowing to LAT (Lietuvos Aukščiausiasis Teismas / Supreme Court), LVAT (Lietuvos vyriausiasis administracinis teismas / Supreme Administrative Court), or LApT (Lietuvos apeliacinis teismas / Court of Appeal). Pass court as exactly one of: LAT, LVAT, LApT. For general Lithuanian court practice across all courts, prefer search-case-law instead. Search in three time periods if needed (same as broad case law search): 1. First call with dateFrom set to 3 years ago. 2. If no results, call again with dateFrom 6 years ago and dateTo 3 years ago. 3. If still no results, call one last time with dateTo 6 years ago (no dateFrom). The vector search query MUST be in Lithuanian. Expand abbreviations and add alternative terms in brackets. To batch several alternative queries in one call, keep one in vectorSearchQuery and put the rest in additionalVectorSearchQueries; they are searched in parallel, round-robin interleaved, deduped, and each snippet includes matchedQueries. Each distinct query adds up to 8 snippets (maximum 24 total). CITING SOURCES: In your answer, ALWAYS link every source you rely on whenever a URL is available. When a result item includes a `sourceLink` field, cite it as a markdown link using the exact Vasara URL, e.g. `[case number or law title](sourceLink)`. For organization website results, link the exact external URL returned. Never present a legal source as plain text when a link can be included, and never invent or alter URLs. ## Vasara source links - Legal-corpus `sourceLink` values are authenticated Vasara URLs (`/mcp/chunk/<token>` or `/mcp/document/<token>`). Copy them verbatim into markdown links: `[descriptive label](sourceLink)`. - Project, project-document, and insight-grid `sourceLink` values are authenticated Vasara URLs (`/mcp/project/<token>`, `/mcp/project-document/<token>`, `/mcp/insight-grid/<token>`). Copy them verbatim; they open the existing project UI after login. - Prefer `sourceLink` / `citationMarkdown` over `citationToken` or inventing `/project/...` paths with raw UUIDs. - Organization website search results still use the exact external `https://` URLs returned by the tool. Do not rewrite those into Vasara links. Before legal research, read the `getLegalResearchInstructions` tool description for the full protocol (tool order, parallel batching, persistence, citations).
search-specific-court-case-law
REQUIRED when the user must choose a project and/or insight grid. Opens an interactive picker UI (MCP Apps) so the user can click a project from a list — preferred over asking them to type a name in chat. Call this whenever: the named project is ambiguous/missing, or there are multiple projects and the user needs to pick one. Use mode=project for project-only work (documents, “what is this project about?”). Use mode=grid when a projectId is known and only an insight grid is needed. Use mode=projectAndGrid when both must be chosen. For mode=grid, pass projectId (opaque token from list-projects). Returned projectId / gridId are opaque tokens for subsequent tools — never raw UUIDs. After the user picks, pass those tokens as args (projectId on list/search tools; gridId on grid tools). Do not substitute a prose list of project names for this tool. CITING SOURCES: In your answer, ALWAYS link every source you rely on whenever a URL is available. When a result item includes a `sourceLink` field, cite it as a markdown link using the exact Vasara URL, e.g. `[case number or law title](sourceLink)`. For organization website results, link the exact external URL returned. Never present a legal source as plain text when a link can be included, and never invent or alter URLs. ## Vasara source links - Legal-corpus `sourceLink` values are authenticated Vasara URLs (`/mcp/chunk/<token>` or `/mcp/document/<token>`). Copy them verbatim into markdown links: `[descriptive label](sourceLink)`. - Project, project-document, and insight-grid `sourceLink` values are authenticated Vasara URLs (`/mcp/project/<token>`, `/mcp/project-document/<token>`, `/mcp/insight-grid/<token>`). Copy them verbatim; they open the existing project UI after login. - Prefer `sourceLink` / `citationMarkdown` over `citationToken` or inventing `/project/...` paths with raw UUIDs. - Organization website search results still use the exact external `https://` URLs returned by the tool. Do not rewrite those into Vasara links.
select-project-or-grid
How do I improve a ChatGPT Plugin's discoverability?
The levers are the listing surface agents actually read: names, descriptions, keywords, tool metadata, and registry health. Which lever matters depends on where discovery breaks, which is what continuous measurement shows.
What are Vasara alternatives on ChatGPT?
As of 2026-09-13, Vasara competes with AI Attorney, AL WAKEELO, Alizé, Appealbase, Açık Silivri Havadis, BIA Edge, CiteCheck, CiteLaw, CourtListener, Craime, Descrybe Legal Engine, DirectCase Legal Research, ElevenFlo, F-AI Contract Template Finder, Folium Jurisprudencia Chilena, Fontis, GovQuery, IAJUS, IFG, Juridata, Lawstronaut, Legal Data Hunter, Legalcode, LegisGraph, LegisRatio, Letra da Lei, LibreJustice, Midpage Legal Research, Nylon, OpenRegs: Regulatory Research, Policy Doctor, realLaw AI, Red Judicial, Remedy Legal, Simpliciter AI, Special Education Law, TaxGraph, TaxMCP, Trellis Law in ChatGPT Legal Research Engines, ranked by public Discoverability Score.
Where is this profile measured?
This profile uses the geography attached to the latest public registry snapshot: US. Locale tags are intentionally omitted.