Skip to main content
Glama
Sign In

Avokata: Lithuanian law & court practice

by com.avokata
OverviewDiscussionsAdmin

What the corpus holds, per area

describe
Read-onlyIdempotent

What this service holds and how complete it is: every source with its date, coverage per legal area with the thin ones named (Constitutional Court, CJEU, first-instance criminal judgments, secondary legislation), the court hierarchy, each court's case-number formats and the EU-governed areas whose EU acts search_law also reads. Call it before telling a user that nothing exists on a topic. It does not search: whether a particular act or ruling is held is search_law's or search_practice's answer, and this connection's sign-in and limits are whoami's. Omit section for the overview; a section returns one block whole. Example arguments: {"section": "coverage"}.

Input Schema

NameRequiredDescriptionDefault
sectionNoLeave empty for the overview (sources, coverage per area, a one-screen coverage census). A section returns one block whole: `scope` (every coverage class with its method, gap and ETA), `register` (the e-TAR mirror), `coverage` (each area's counts and how they were measured), `currency` (acts served in an edition older than an amendment in force), `eu` (each EU area's acts, held or not).
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.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / section / description
      Previous value: -"Leave empty for the overview (sources, coverage per area, a one-screen coverage census). `scope` returns the full census: every class of document with its source, method, served and known counts, gap and ETA."New value: +"Leave empty for the overview (sources, coverage per area, a one-screen coverage census). A section returns one block whole: `scope` (every coverage class with its method, gap and ETA), `register` (the e-TAR mirror), `coverage` (each area's counts and how they were measured), `currency` (acts served in an edition older than an amendment in force), `eu` (each EU area's acts, held or not)."
  2. Changed1 schema field changed
    • addedInput schema / properties / section
      Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "Leave empty for the overview (sources, coverage per area, a one-screen coverage census). `scope` returns the full census: every class of document with its source, method, served and known counts, gap and ETA.",
+  "title": "Section"
+}
  3. Added

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already establish read-only, idempotent, non-destructive and closed-world, so the safety bar is low. The description adds real behavioral context beyond them: which corpus areas are thin, that omitting `section` returns an overview while a section returns one block whole, and that sign-in/limits live elsewhere. It stops short of describing response shape or size, hence 4 rather than 5.

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 core purpose and routes to alternatives efficiently, with zero filler sentences. The opening sentence is a long enumerated clause that packs many items at once, which costs some readability but no wasted words.

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

Completeness4/5

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

For a two-parameter, no-output-schema read tool, the description covers purpose, trigger, non-uses, section behavior and an example call. It leaves the actual returned block structure unspecified, which matters somewhat given there is no output schema, but the section enumeration largely compensates.

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

Parameters3/5

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

Schema description coverage is 100% and the `section` field already enumerates scope/register/coverage/currency/eu with definitions, so the description largely restates that. The only added meaning is the example argument and the framing of a section being returned "whole"; baseline 3 applies when the schema does the heavy lifting.

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 resource (the corpus: sources, dates, per-area coverage, court hierarchy, case-number formats) and explicitly delimits itself from search_law, search_practice and whoami, so an agent can separate it from those siblings without reading 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?

Gives a concrete trigger ("Call it before telling a user that nothing exists on a topic") plus explicit when-not guidance: it does not search, and act-level existence questions belong to search_law/search_practice, while sign-in and limits belong to whoami. Alternatives are named with the conditions that select them.

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