Skip to main content
Glama
Sign In

Avokata: Lithuanian law & court practice

by com.avokata
OverviewDiscussionsAdmin

Document and contents

get_document
Read-onlyIdempotent

Sign-in required: call connect(email) and connect_verify first (free, one email) unless this connection is already signed in. A document's identity and its table of contents (turinys), WITHOUT its text. Call this before reading: the Civil Code (Civilinis kodeksas) runs to 1.7 million characters. Ids come from search results (įstatymas or nutartis). An ECHR id (coe.hudoc:) or application number gives the case's catalogue card: Avokata holds no ECHR text - read it at text_availability.where (HUDOC).

Input Schema

NameRequiredDescriptionDefault
partNoOptional: one chapter or approved document of a long act - a label from its contents' `location` (`IV SKYRIUS`, `Darbo laiko ir poilsio laiko ypatumų ... aprašas`). Lists that part's units only; without it a long act's contents come by chapter.
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.
document_idYesThe `id` of a search hit, or the `document.id` beside it. NOT `document.number`, which is the act's official number (`XIII-2221`) and is not an id.
jurisdictionNoWhich jurisdiction the id belongs to (`LT`). Omit for the account's own.
contents_limitNoOptional: unit rows per page with `contents_offset`, default 400, at most 1,000 (a page also ends early to stay within the answer's size, and says where the next one starts).
contents_offsetNoOptional: list the contents as unit rows from this position (0 = the first unit). A long document's contents otherwise come by chapter; every answer states the true total (`contents_page.units_total`) and the next offset.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / contents_limit
      Added value: +{
+  "anyOf": [
+    {
+      "type": "integer"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "Optional: unit rows per page with `contents_offset`, default 400, at most 1,000 (a page also ends early to stay within the answer's size, and says where the next one starts).",
+  "title": "Contents Limit"
+}
    • addedInput schema / properties / contents_offset
      Added value: +{
+  "anyOf": [
+    {
+      "type": "integer"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "Optional: list the contents as unit rows from this position (0 = the first unit). A long document's contents otherwise come by chapter; every answer states the true total (`contents_page.units_total`) and the next offset.",
+  "title": "Contents Offset"
+}
  2. Changed1 schema field changed
    • addedInput schema / properties / part
      Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "Optional: one chapter or approved document of a long act - a label from its contents' `location` (`IV SKYRIUS`, `Darbo laiko ir poilsio laiko ypatumų ... aprašas`). Lists that part's units only; without it a long act's contents come by chapter.",
+  "title": "Part"
+}
  3. Changed1 schema field changed
    • removedInput schema / properties / part
      Removed value: -{
-  "anyOf": [
-    {
-      "type": "string"
-    },
-    {
-      "type": "null"
-    }
-  ],
-  "default": null,
-  "description": "Optional: one chapter or approved document of a long act - a label from its contents' `location` (`IV SKYRIUS`, `Darbo laiko ir poilsio laiko ypatumų ... aprašas`). Lists that part's units only; without it a long act's contents come by chapter.",
-  "title": "Part"
-}
  4. Changed1 schema field changed
    • addedInput schema / properties / part
      Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "Optional: one chapter or approved document of a long act - a label from its contents' `location` (`IV SKYRIUS`, `Darbo laiko ir poilsio laiko ypatumų ... aprašas`). Lists that part's units only; without it a long act's contents come by chapter.",
+  "title": "Part"
+}
  5. Added

TDQS

A4.6/5.0
Behavior5/5

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

Annotations already declare readOnlyHint/idempotentHint, so the bar is lower, yet the description adds substantive context beyond them: sign-in prerequisites, the size cutoff that motivates calling this first, and the important limit that Avokata holds no ECHR text, directing the agent to text_availability.where instead.

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?

Front-loads the auth prerequisite, then the core purpose and scope limits. Dense but nearly every clause carries information; the sign-in sentence is long but justified for a gated tool.

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?

With no output schema, the description still conveys the return shape: identity plus contents, chapter-wise listing for long acts, and that answers state true totals and next offsets. Combined with the ECHR fallback pointer, an agent has enough to call and interpret it correctly.

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 baseline is 3; the description adds real value on top by clarifying that ids come from search results and that document_id is NOT document.number (the official act number), a distinction the schema leaves implicit. Pagination and part semantics are left largely to the schema.

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+resource: returns a document's identity and its table of contents (turinys), explicitly WITHOUT the text. That negative scope cleanly separates it from text-reading siblings like read_source_text or read_paragraphs without needing to name them.

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

Usage Guidelines4/5

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

Gives explicit sequencing ('Call this before reading') plus a concrete trigger (Civil Code at 1.7M characters) and prerequisite auth steps (connect/connect_verify). It does not name the sibling to call next, but the when-to-use condition is unambiguous.

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

All Avokata: Lithuanian law & court practice toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources