Skip to main content
Glama
Sign In

Avokata: Lithuanian law & court practice

by com.avokata
OverviewDiscussionsAdmin

List playbooks and jobs

list_workflows
Read-onlyIdempotent

Sign-in required: call connect(email) and connect_verify first (free, one email) unless this connection is already signed in. List the playbooks available: the ones Avokata ships and any this account has written. For one task, find_workflow is quicker: it names the one that fits. scope='mine' shows this account's own library with versions and use.

Input Schema

NameRequiredDescriptionDefault
limitNoHow many playbooks to return, default 50 (jobs are always listed whole: there are few and they come first).
scopeNo`all` (the default), `mine` (only this account's own, with versions, uses and last use) or `shipped` (the studio's playbooks).all
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.
max_charsNoA hard cap on the answer's size in characters, default 15000. Rows are dropped from the end to fit, and `truncated` says how many and how to get them.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / scope
      Added value: +{
+  "default": "all",
+  "description": "`all` (the default), `mine` (only this account's own, with versions, uses and last use) or `shipped` (the studio's playbooks).",
+  "enum": [
+    "all",
+    "mine",
+    "shipped"
+  ],
+  "title": "Scope",
+  "type": "string"
+}
  2. Changed1 schema field changed
    • changedInput schema / properties / max_chars / description
      Previous value: -"A hard cap on the answer's size in characters, default 12000. Rows are dropped from the end to fit, and `truncated` says how many and how to get them."New value: +"A hard cap on the answer's size in characters, default 15000. Rows are dropped from the end to fit, and `truncated` says how many and how to get them."
  3. Changed1 schema field changed
    • 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 to fit, and `truncated` says how many and how to get them."New value: +"A hard cap on the answer's size in characters, default 12000. Rows are dropped from the end to fit, and `truncated` says how many and how to get them."
  4. Changed3 schema fields changed
    • addedInput schema / properties / limit
      Added value: +{
+  "default": 50,
+  "description": "How many playbooks to return, default 50 (jobs are always listed whole: there are few and they come first).",
+  "title": "Limit",
+  "type": "integer"
+}
    • 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 to fit, and `truncated` says how many and how to get them.",
+  "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."
  5. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already establish readOnly/idempotent/non-destructive, so the safety profile is covered. The description adds behavior the annotations cannot: an auth prerequisite sequence, the session-token persistence requirement across calls, and truncation behavior via max_chars. It does not explain result ordering beyond the schema's note that jobs come first, so it falls just short of 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 sign-in prerequisite, then the purpose, then the sibling routing hint, in three compact sentences. Slightly dense parenthetical asides, but each sentence carries information an agent needs.

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 read-only list tool with zero required parameters and no output schema, the description covers auth, result sources, scope selection, sibling routing, and truncation handling. Only the return shape/ordering is left implicit (and partially covered by the schema), so it is nearly complete.

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%, so each parameter (limit, scope, session, max_chars) is already fully documented in the schema. The description only restates scope='mine' ("shows this account's own library with versions and use"), which largely duplicates schema text and adds no new format or constraint details. Baseline 3 is appropriate.

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?

"List the playbooks available: the ones Avokata ships and any this account has written" names a specific verb (list) and resource (playbooks), and clarifies the two sources of results. It explicitly distinguishes itself from find_workflow, which the agent could otherwise confuse with a library-listing call.

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?

It states the precondition (sign-in via connect/connect_verify unless already signed in) and the alternative path ("For one task, find_workflow is quicker: it names the one that fits"), plus the condition that selects scope='mine'. Nothing about when to choose this tool is left to inference.

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