Avokata: Lithuanian law for your agent

Open a playbook or job

get_workflow

Read-onlyIdempotent

Sign-in required: call connect(email) and connect_verify first (free, one email) unless this connection is already signed in. Open one workflow as a PLAN bound to the task: the ordered tool calls with the act number, case number or date from task filled in and every other slot left open, the principles and what the result looks like - under 2,000 characters. You run the steps yourself, in order. detail='full' adds the prose.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`task`	No	The user's task in a sentence. Exact identifiers in it (an act number `XII-2603`, a case number `e3K-3-105-684/2019`, a date `2021-03-01`) are filled into the plan's slots; every other slot stays open for you to fill.
`detail`	No	`plan` (the default): the ordered calls, principles and outputs, under 2,000 characters. `full` adds the prose body the plan was copied from.	plan
`session`	No	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.
`workflow_id`	No	Which workflow to open, by the `workflow_id` from `find_workflow` or `list_workflows` - e.g. `still-good-law`, `job-matter-memo`. A bare id is the playbook; a job is `job-<id>`.

Schema Changelog

Changes observed during successful MCP inspections.

Changed7 schema fields changedOct 7, 2026

addedInput schema / properties / detail

Added value: +{
+  "default": "plan",
+  "description": "`plan` (the default): the ordered calls, principles and outputs, under 2,000 characters. `full` adds the prose body the plan was copied from.",
+  "enum": [
+    "plan",
+    "full"
+  ],
+  "title": "Detail",
+  "type": "string"
+}

addedInput schema / properties / task

Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "The user's task in a sentence. Exact identifiers in it (an act number `XII-2603`, a case number `e3K-3-105-684/2019`, a date `2021-03-01`) are filled into the plan's slots; every other slot stays open for you to fill.",
+  "title": "Task"
+}

addedInput schema / properties / workflow_id / anyOf

Added value: +[
+  {
+    "type": "string"
+  },
+  {
+    "type": "null"
+  }
+]

addedInput schema / properties / workflow_id / default
```
Added value: +null
```

changedInput schema / properties / workflow_id / description

Previous value: -"Which playbook to read, by the `workflow_id` from `list_workflows` - e.g. `still-good-law`, `matter-digest`."New value: +"Which workflow to open, by the `workflow_id` from `find_workflow` or `list_workflows` - e.g. `still-good-law`, `job-matter-memo`. A bare id is the playbook; a job is `job-<id>`."

removedInput schema / properties / workflow_id / type
```
Removed value: -"string"
```
removedInput schema / required
```
Removed value: -[
-  "workflow_id"
-]
```

Changed1 schema field changedSep 24, 2026

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."

First observedSep 24, 2026

TDQS

Score is being calculated.

All Avokata: Lithuanian law for your agent tools Inspect

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

Need Help?