Skip to main content
Glama

Avokata: Lithuanian law for your agent

by com.avokata
OverviewDiscussionsAdmin

List playbooks and jobs

list_workflows
Read-onlyIdempotent

List the playbooks available: the ones Avokata ships and any this account has written. Call this when you want the procedure for a legal task rather than inventing one.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoHow many playbooks to return, default 50 (jobs are always listed whole: there are few and they come first).
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 8000. 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. 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."
  2. First observed

TDQS

A4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the description does not need to cover safety. It adds useful context about included playbooks but does not disclose additional behavioral details such as jobs handling or truncation beyond what the schema already provides.

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

Conciseness5/5

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

Two sentences with no filler. The core purpose comes first, and the usage trigger is condensed into the second sentence, earning its place.

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 simple read-only list tool with a fully documented schema, the description plus schema cover the needed context. It does not explicitly mention that jobs are included, despite the title, and there is no output schema, but the max_chars parameter describes truncation behavior sufficiently.

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?

The schema has 100% coverage with detailed parameter descriptions, including default values and the meaning of truncation. The tool description itself adds no parameter-level semantics, so the schema is doing the necessary work.

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?

The description states a specific action ('List the playbooks available') with a clear scope: Avokata-shipped playbooks plus ones the account authored. It also ties the tool to retrieving a legal procedure, which distinguishes it from searching law or practice materials.

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?

It provides an explicit trigger: 'Call this when you want the procedure for a legal task rather than inventing one.' It does not name sibling tools like get_workflow as alternatives, but the guidance is clear enough for selecting this tool.

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 for your agent 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