Skip to main content
Glama

Avokata: Lithuanian law for your agent

by com.avokata
OverviewDiscussionsAdmin

Finish signing in

connect_verify

Finish signing in: call right after connect(email) with the request_id and no code; it waits for the user's Confirm click (if it returns waiting, call again, never ask the user). Or pass the code they read you. Also takes a key the user already holds (api_key) to use that account here.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
codeNoThe six-digit code from the email, only if the user reads it to you instead of clicking Confirm.
api_keyNoA key the user already holds (`avk_...`, or an earlier `dic_...`), to use that account in this conversation. Not needed after an email sign-in.
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.
request_idNoThe `request_id` that `connect(email=...)` returned. Call right away with no code: it waits for the user's Confirm click.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / api_key / description
      Previous value: -"A key the user already holds (`dic_...`), to use that account in this conversation. Not needed after an email sign-in."New value: +"A key the user already holds (`avk_...`, or an earlier `dic_...`), to use that account in this conversation. Not needed after an email sign-in."
  2. Changed8 schema fields changed
    • addedInput schema / properties / api_key / anyOf
      Added value: +[
+  {
+    "type": "string"
+  },
+  {
+    "type": "null"
+  }
+]
    • addedInput schema / properties / api_key / default
      Added value: +null
    • changedInput schema / properties / api_key / description
      Previous value: -"A key issued earlier by `connect`, in the form `dic_...`. Only needed to resume an account in a NEW conversation; a fresh `connect` is the normal path."New value: +"A key the user already holds (`dic_...`), to use that account in this conversation. Not needed after an email sign-in."
    • removedInput schema / properties / api_key / type
      Removed value: -"string"
    • addedInput schema / properties / code
      Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "The six-digit code from the email, only if the user reads it to you instead of clicking Confirm.",
+  "title": "Code"
+}
    • addedInput schema / properties / request_id
      Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "The `request_id` that `connect(email=...)` returned. Call right away with no code: it waits for the user's Confirm click.",
+  "title": "Request Id"
+}
    • addedInput schema / properties / session
      Added value: +{
+  "description": "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.",
+  "type": "string"
+}
    • removedInput schema / required
      Removed value: -[
-  "api_key"
-]
  3. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations declare a non-read-only, non-idempotent operation. The description adds important behavioral flow beyond that: it waits for the user's Confirm click, tells the agent to call again on 'waiting' without asking the user, and explains the api_key path to reuse an existing account. It does not discuss the session parameter or failure outcomes, but adds substantial context.

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?

The description is front-loaded with a colon and then enumerates alternatives clearly. Parentheticals are useful (retry behavior, never ask user) and every sentence earns its place, though the final sentence is slightly dense.

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 multi-step auth tool with no output schema, the description covers the primary flow, an alternative code path, a key-based path, and retry semantics. It does not mention the session parameter or what happens after success/failure, but the schema documents session and the annotations cover safety, so it is complete enough for correct invocation.

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 schema descriptions are already detailed. The description's parameter guidance (request_id from connect, code if read, api_key for an existing account) largely repeats the schema and adds no new syntax or format details; it also omits the session parameter entirely. 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?

States a specific action ('Finish signing in') and explicitly positions itself as the follow-up to connect(email), so the agent can distinguish it from the sibling connect tool without opening the 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 explicit when-to-use instructions for three scenarios: call right after connect(email) with request_id and no code, pass the code if read aloud, or use an api_key. It also covers the waiting/retry loop and tells the agent never to ask the user, leaving nothing 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 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