Skip to main content
Glama

Avokata: Lithuanian law & court practice

Search Lithuanian law

search_law
Read-onlyIdempotent

Sign-in required: call connect(email) and connect_verify first (free, one email) unless this connection is already signed in. Find the statutory provision (teisės akto straipsnis) that governs a question. PASS THE QUERY IN THE LANGUAGE THE LAW IS WRITTEN IN. Lithuanian law: in Lithuanian. An English query is not translated for you and does not work - measured 2026-08-28 on 23 questions a lawyer had answered from the corpus, Lithuanian found the confirmed article for 10 of them and English for 0, and the English attempts did not come back empty, they came back wrong. If the user writes in another language, translate INTO Lithuanian and use the term of art a Lithuanian lawyer would type: ieškinio senaties terminas, darbo sutarties nutraukimas, nuomos sutartis, servitutas, juridinio asmens pertvarkymas. EU and international acts: Lithuanian where a Lithuanian text is held, else the source language; every result says its lang, and a translation you give the user is labelled as yours with its source. Searches acts and codes (įstatymai ir kodeksai) in the consolidated version in force now. Returns pinpoints (article numbers), not summaries. Follow up with read_paragraphs to read the text, or cited_by to see how the courts have read it. jurisdictions accepts several for a matter that spans countries. codes names the code the question belongs to (CPK, BPK, ABTĮ, CK, DK) and you should pass it for anything PROCEDURAL. Every procedural code has articles with the same headings, different numbers and different time limits, so an answer from the wrong one looks exactly like an answer from the right one: measured 2026-08-28, four of ten procedural questions returned their top hit from the wrong code, including a civil cassation deadline answered from the criminal procedure code. jurisdictions selects the law's scope, not the user's language; there is no separate language argument. For an article's wording on a past date, find its id here and use read_paragraphs with on_date. The complete search answer obeys max_chars; response_budget identifies deferred metadata and its recovery. Example arguments: {"query": "ieškinio senaties terminas", "jurisdictions": ["LT"], "codes": ["CK"], "limit": 5}.

Input Schema

NameRequiredDescriptionDefault
alsoNoOther phrasings of the SAME question, each fused as its own ranking - up to 4. Pass one only when it is a genuinely DIFFERENT ANGLE: the legal term of art, or the noun phrase a provision heading would be written in. Do NOT pass the same sentence reworded, which was measured to make results worse (hit@5 12 to 10). You are the one who knows what a different angle on this question is, which is why this is offered rather than applied automatically.
codesNoRestrict to named codes by their short form (`CK`, `CPK`, `BK`, `DK`). The fastest way to ask 'what does the Civil Code say about this'.
limitNoHow many passages to return, default 10. Each carries its own pinpoint, so a larger number is more context rather than more documents.
queryYesThe question or the provision, in the language of the law asked about: IN LITHUANIAN for Lithuanian law (an English query returns unrelated results rather than none); EU or international material in Lithuanian where it has a Lithuanian text, else in its source language (English, French). Both forms work: a citation (`CK 6.217`) or a phrase (`esminis sutarties pažeidimas`). There is no separate article filter, and no date filter: this tool answers about law in force NOW.
detailNo`compact` (the default) returns each passage with its pinpoint and an excerpt of up to ~250 characters around your terms (narrower, never below a sentence piece of ~130, when many rows share max_chars), plus `text_chars`; read the whole text with read_paragraphs(document_id=<row id>). `full` returns the whole text of every row.compact
sessionNoThe `session` value the sign-in returned. Pass it on every call in this conversation, so the sign-in survives however this client handles connections; omit it when the user connected with Sign in (OAuth) or a key.
in_forceNoTrue (the default) searches only acts in force. Set false to include repealed ones - which is a different question from what governed on a past date; for that, find the act and ask `check_validity` with `on_date`.
act_typesNoNarrow by the register's own type of act, e.g. `Įstatymas`, `Kodeksas`, `Nutarimas`. Omit to search every type.
max_charsNoA hard cap on the answer's size in characters, default 15000. Every row is first narrowed (a ~150-character excerpt), then rows are dropped from the end (the lowest-ranked) to fit, and `truncated` says how many and how to get them; data_as_of, notes and caveats are never cut.
act_numberNoSearch inside ONE act by its official register number (`XII-2603`), a Government resolution's or an order's number (`496`, `Nr. 496`, with its year to choose among resolutions of other years: `2017 m. birželio 21 d. nutarimas Nr. 496`) or a code abbreviation the map knows (`DK`, `CK`, `CPK`). Lawyers search by Nr.; this is how you restrict to that act without naming every article. A number or an abbreviation only: an act you know by its title goes in `query`.
occurrencesNoTrue lists EVERY provision of one act whose words hold the phrase in `query`, in any inflection (each word by its stem; `taisykl*` names a stem), with a count and the forms found - an exhaustive list, not a ranking. Needs the act as `act_number` (or one `codes` entry). Use it to check "X is mentioned only in articles ...".
jurisdictionsNoWhich jurisdictions to search, as codes (`LT`). Omit for the account's own. Adding a country you do not hold does not fail; the answer names what was unavailable.
include_amending_actsNoFalse (the default) leaves out amending acts (`... pakeitimo įstatymas`): an amending act says what changed, not what the law is, and this tool answers which provision governs. The answer says how many it left out. Set true to date a change or read the amendment itself.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / detail / description
      Previous value: -"`compact` (the default) returns each passage with its pinpoint and a ~250-character excerpt around your terms, plus `text_chars`; read the whole text with read_paragraphs(document_id=<row id>). `full` returns the whole text of every row."New value: +"`compact` (the default) returns each passage with its pinpoint and an excerpt of up to ~250 characters around your terms (narrower, never below a sentence piece of ~130, when many rows share max_chars), plus `text_chars`; read the whole text with read_paragraphs(document_id=<row id>). `full` returns the whole text of every row."
  2. Changed1 schema field changed
    • addedInput schema / properties / occurrences
      Added value: +{
      +  "default": false,
      +  "description": "True lists EVERY provision of one act whose words hold the phrase in `query`, in any inflection (each word by its stem; `taisykl*` names a stem), with a count and the forms found - an exhaustive list, not a ranking. Needs the act as `act_number` (or one `codes` entry). Use it to check \"X is mentioned only in articles ...\".",
      +  "title": "Occurrences",
      +  "type": "boolean"
      +}
  3. Changed1 schema field changed
    • changedInput schema / properties / query / description
      Previous value: -"The question or the provision, IN LITHUANIAN - the corpus is Lithuanian and an English query returns unrelated results rather than none. Both forms work: a citation (`CK 6.217`) or a phrase (`esminis sutarties pažeidimas`). There is no separate article filter, and no date filter: this tool answers about law in force NOW."New value: +"The question or the provision, in the language of the law asked about: IN LITHUANIAN for Lithuanian law (an English query returns unrelated results rather than none); EU or international material in Lithuanian where it has a Lithuanian text, else in its source language (English, French). Both forms work: a citation (`CK 6.217`) or a phrase (`esminis sutarties pažeidimas`). There is no separate article filter, and no date filter: this tool answers about law in force NOW."
  4. Changed1 schema field changed
    • changedInput schema / properties / act_number / description
      Previous value: -"Search inside ONE act by its official register number (`XII-2603`), a Government resolution's or an order's number (`496`, `Nr. 496`, with its year to choose among resolutions of other years: `2017 m. birželio 21 d. nutarimas Nr. 496`) or a code abbreviation the map knows (`DK`, `CK`, `CPK`). Lawyers search by Nr.; this is how you restrict to that act without naming every article."New value: +"Search inside ONE act by its official register number (`XII-2603`), a Government resolution's or an order's number (`496`, `Nr. 496`, with its year to choose among resolutions of other years: `2017 m. birželio 21 d. nutarimas Nr. 496`) or a code abbreviation the map knows (`DK`, `CK`, `CPK`). Lawyers search by Nr.; this is how you restrict to that act without naming every article. A number or an abbreviation only: an act you know by its title goes in `query`."
  5. Changed1 schema field changed
    • changedInput schema / properties / act_number / description
      Previous value: -"Search inside ONE act by its official register number (`XII-2603`) or a code abbreviation the map knows (`DK`, `CK`, `CPK`). Lawyers search by Nr.; this is how you restrict to that act without naming every article."New value: +"Search inside ONE act by its official register number (`XII-2603`), a Government resolution's or an order's number (`496`, `Nr. 496`, with its year to choose among resolutions of other years: `2017 m. birželio 21 d. nutarimas Nr. 496`) or a code abbreviation the map knows (`DK`, `CK`, `CPK`). Lawyers search by Nr.; this is how you restrict to that act without naming every article."
  6. Changed1 schema field changed
    • changedInput schema / properties / max_chars / description
      Previous value: -"A hard cap on the answer's size in characters, default 12000. Every row is first narrowed (a ~150-character excerpt), then rows are dropped from the end (the lowest-ranked) to fit, and `truncated` says how many and how to get them; data_as_of, notes and caveats are never cut."New value: +"A hard cap on the answer's size in characters, default 15000. Every row is first narrowed (a ~150-character excerpt), then rows are dropped from the end (the lowest-ranked) to fit, and `truncated` says how many and how to get them; data_as_of, notes and caveats are never cut."
  7. Changed2 schema fields changed
    • changedInput schema / properties / detail / description
      Previous value: -"`compact` (the default) returns each passage with its pinpoint and a ~400-character excerpt around your terms, plus `text_chars`; read the whole text with read_paragraphs(document_id=<row id>). `full` returns the whole text of every row."New value: +"`compact` (the default) returns each passage with its pinpoint and a ~250-character excerpt around your terms, plus `text_chars`; read the whole text with read_paragraphs(document_id=<row id>). `full` returns the whole text of every row."
    • changedInput schema / properties / max_chars / description
      Previous value: -"A hard cap on the answer's size in characters, default 8000. Rows are dropped from the end (the lowest-ranked) to fit, and `truncated` says how many and how to get them; data_as_of, notes and caveats are never cut."New value: +"A hard cap on the answer's size in characters, default 12000. Every row is first narrowed (a ~150-character excerpt), then rows are dropped from the end (the lowest-ranked) to fit, and `truncated` says how many and how to get them; data_as_of, notes and caveats are never cut."
  8. Changed1 schema field changed
    • changedInput schema / properties / query / description
      Previous value: -"The question or the provision, IN LITHUANIAN - the corpus is Lithuanian and an English query returns confident nonsense rather than nothing. Both forms work: a citation (`CK 6.217`) or a phrase (`esminis sutarties pažeidimas`). There is no separate article filter, and no date filter: this tool answers about law in force NOW."New value: +"The question or the provision, IN LITHUANIAN - the corpus is Lithuanian and an English query returns unrelated results rather than none. Both forms work: a citation (`CK 6.217`) or a phrase (`esminis sutarties pažeidimas`). There is no separate article filter, and no date filter: this tool answers about law in force NOW."
  9. Changed4 schema fields changed
    • addedInput schema / properties / detail
      Added value: +{
      +  "default": "compact",
      +  "description": "`compact` (the default) returns each passage with its pinpoint and a ~400-character excerpt around your terms, plus `text_chars`; read the whole text with read_paragraphs(document_id=<row id>). `full` returns the whole text of every row.",
      +  "enum": [
      +    "compact",
      +    "full"
      +  ],
      +  "title": "Detail",
      +  "type": "string"
      +}
    • addedInput schema / properties / include_amending_acts
      Added value: +{
      +  "default": false,
      +  "description": "False (the default) leaves out amending acts (`... pakeitimo įstatymas`): an amending act says what changed, not what the law is, and this tool answers which provision governs. The answer says how many it left out. Set true to date a change or read the amendment itself.",
      +  "title": "Include Amending Acts",
      +  "type": "boolean"
      +}
    • addedInput schema / properties / max_chars
      Added value: +{
      +  "anyOf": [
      +    {
      +      "type": "integer"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ],
      +  "default": null,
      +  "description": "A hard cap on the answer's size in characters, default 8000. Rows are dropped from the end (the lowest-ranked) to fit, and `truncated` says how many and how to get them; data_as_of, notes and caveats are never cut.",
      +  "title": "Max Chars"
      +}
    • changedInput schema / properties / session / description
      Previous value: -"The `session` value connect returned, when this client keeps no connection session. Pass it on every Avokata call in this conversation; omit it when the client sends a key."New value: +"The `session` value the sign-in returned. Pass it on every call in this conversation, so the sign-in survives however this client handles connections; omit it when the user connected with Sign in (OAuth) or a key."
  10. First observed

TDQS

A4.8/5.0
Behavior5/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare read-only, idempotent, closed-world, non-destructive, so the safety bar is low — yet the description adds substantial operational context beyond them: the sign-in precondition, the measured failure mode of English queries ('came back wrong', not empty), the wrong-code failure mode for procedural questions, what max_chars truncates and what it never cuts, and how amending acts are excluded by default.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Dense but almost every sentence carries decision-relevant information, and the language and code pitfalls are front-loaded. It loses a point because the auth preamble occupies the opening slot ahead of the purpose statement, and the language rule is restated three times (body, query description, jurisdictions note), making it longer than the tool's complexity strictly requires.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a 13-parameter tool with no output schema, the description covers everything an agent needs: what a result row contains (pinpoint, lang label, text_chars), how to read full text, how the character budget and `truncated`/`response_budget` behave, and the in-force/amendment semantics that determine answer correctness.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the schema already documents all 13 parameters; the baseline would be 3. The description nonetheless adds real semantics the schema does not: `jurisdictions` selects the law's scope and is not a language argument, `codes` must be passed for anything procedural and why, and a worked example argument set is supplied at the end.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource — 'Find the statutory provision (teisės akto straipsnis) that governs a question' — and immediately scopes it ('consolidated version in force now', 'returns pinpoints, not summaries'). It also routes to the natural siblings (read_paragraphs, cited_by, check_validity) so an agent can tell it apart from the surrounding tools without opening any schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicit when-to-use and when-to-use-something-else: read_paragraphs for text, cited_by for judicial reading, check_validity with on_date for past-date validity, occurrences for exhaustive phrase checks, in_force=false vs. past-date as 'a different question'. It also gives a hard prerequisite (connect/connect_verify) and a routing rule for procedural questions via `codes`.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources