Skip to main content
Glama
Sign In
Bernstein - Multi-agent orchestration

Bernstein - Multi-agent orchestration

by sipyourdrink-ltd
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

bernstein_run_status

Poll a run started with bernstein_run to read its status from the local run journal and audit evidence. Pass the task_id or run_id to check progress without modifying any files.

Instructions

Poll a verifiable handle for a run started with bernstein_run. Accepts either identifier that call returned: the task_id or the run_id. Reads the local run journal and audit evidence without changing them. Host effects: reads files.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "run_id": "<run_id>"
    },
    "name": "bernstein_run_status"
  }
}

Input Schema

NameRequiredDescriptionDefault
run_idYesThe run to project. Either the task_id or the run_id returned by bernstein_run. Resolved journal run id first, then the task id slugified into a journal run id, so both forms reach one journal.
workdirNo

Output Schema

NameRequiredDescriptionDefault
_meterYes
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv3.23.0
    • changedOutput schema / properties / result / anyOf
      Previous value: -[
-  {
-    "additionalProperties": false,
-    "properties": {
-      "chainHead": {
-        "type": "string"
-      },
-      "journalHead": {
-        "type": "string"
-      },
-      "pollToken": {
-        "type": "string"
-      },
-      "progress": {
-        "type": [
-          "object",
-          "null"
-        ]
-      },
-      "progressHash": {
-        "type": "string"
-      },
-      "receiptHash": {
-        "type": "string"
-      },
-      "runId": {
-        "type": "string"
-      },
-      "specRevision": {
-        "type": "string"
-      },
-      "status": {
-        "enum": [
-          "cancelled",
-          "completed",
-          "failed",
-          "input_required",
-          "working"
-        ],
-        "type": "string"
-      },
-      "taskId": {
-        "type": "string"
-      },
-      "traceId": {
-        "type": "string"
-      }
-    },
-    "required": [
-      "chainHead",
-      "journalHead",
-      "pollToken",
-      "progress",
-      "progressHash",
-      "receiptHash",
-      "runId",
-      "specRevision",
-      "status",
-      "taskId",
-      "traceId"
-    ],
-    "type": "object"
-  },
-  {
-    "additionalProperties": true,
-    "properties": {
-      "error": {
-        "type": "string"
-      },
-      "hint": {
-        "type": "string"
-      }
-    },
-    "required": [
-      "error"
-    ],
-    "type": "object"
-  }
-]New value: +[
+  {
+    "additionalProperties": false,
+    "properties": {
+      "chainHead": {
+        "type": "string"
+      },
+      "journalHead": {
+        "type": "string"
+      },
+      "pollToken": {
+        "type": "string"
+      },
+      "progress": {
+        "type": [
+          "object",
+          "null"
+        ]
+      },
+      "progressHash": {
+        "type": "string"
+      },
+      "receiptHash": {
+        "type": "string"
+      },
+      "runId": {
+        "type": "string"
+      },
+      "specRevision": {
+        "type": "string"
+      },
+      "status": {
+        "enum": [
+          "cancelled",
+          "completed",
+          "failed",
+          "input_required",
+          "working"
+        ],
+        "type": "string"
+      },
+      "taskId": {
+        "type": "string"
+      },
+      "traceId": {
+        "type": "string"
+      }
+    },
+    "required": [
+      "chainHead",
+      "journalHead",
+      "pollToken",
+      "progress",
+      "progressHash",
+      "receiptHash",
+      "runId",
+      "specRevision",
+      "status",
+      "taskId",
+      "traceId"
+    ],
+    "type": "object"
+  },
+  {
+    "description": "Authenticated task aggregate returned by administrative run surfaces.",
+    "properties": {
+      "chainHead": {
+        "title": "Chainhead",
+        "type": "string"
+      },
+      "chainVerified": {
+        "const": true,
+        "title": "Chainverified",
+        "type": "boolean"
+      },
+      "goal": {
+        "title": "Goal",
+        "type": "string"
+      },
+      "receiptHash": {
+        "title": "Receipthash",
+        "type": "string"
+      },
+      "runId": {
+        "title": "Runid",
+        "type": "string"
+      },
+      "status": {
+        "enum": [
+          "working",
+          "completed"
+        ],
+        "title": "Status",
+        "type": "string"
+      },
+      "tasks": {
+        "items": {
+          "additionalProperties": {
+            "type": "string"
+          },
+          "type": "object"
+        },
+        "title": "Tasks",
+        "type": "array"
+      },
+      "template": {
+        "const": "administrative",
+        "default": "administrative",
+        "title": "Template",
+        "type": "string"
+      },
+      "tenant_id": {
+        "title": "Tenant Id",
+        "type": "string"
+      }
+    },
+    "required": [
+      "runId",
+      "goal",
+      "tenant_id",
+      "status",
+      "tasks",
+      "chainHead",
+      "chainVerified",
+      "receiptHash"
+    ],
+    "title": "AdministrativeRunStatus",
+    "type": "object"
+  },
+  {
+    "additionalProperties": true,
+    "properties": {
+      "error": {
+        "type": "string"
+      },
+      "hint": {
+        "type": "string"
+      }
+    },
+    "required": [
+      "error"
+    ],
+    "type": "object"
+  }
+]
  2. Changed1 schema field changedv3.15.0
    • changedInput schema / description
      Previous value: -"Poll a verifiable handle for a run started with bernstein_run. Accepts either identifier that call returned: the task_id or the run_id."New value: +"Poll a verifiable handle for a run started with bernstein_run. Accepts either identifier that call returned: the task_id or the run_id. Reads the local run journal and audit evidence without changing them. Host effects: reads files."
  3. Addedv3.11.0

TDQS

A3.9/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does well: it declares this is a read of the local run journal and audit evidence that does not change them, plus an explicit host-effect statement ('reads files'). It does not discuss cost, latency, or what happens for an unknown/expired run id.

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?

Three short sentences, front-loaded with the core purpose and followed by identifier flexibility and side effects. Some redundancy with the identical schema description text, but no wasted prose.

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?

An output schema exists, so return values need not be described, and the description covers the read-only nature and host effects. The only notable gap is the unexplained optional workdir parameter for a tool whose resolution depends on the local journal location.

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 coverage is only 50%, and the description essentially restates the run_id flexibility the schema already documents (task_id or run_id resolution order lives in the schema). The workdir parameter is undocumented in both schema and description, so the description does not compensate for the coverage gap.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb ('Poll') and resource ('a verifiable handle for a run') and ties it explicitly to the originating call bernstein_run, which separates it from siblings like bernstein_run or bernstein_create_task. It does not explicitly contrast with the similarly named bernstein_status, so a 4 rather than a 5.

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?

Gives a clear trigger — use this after bernstein_run has returned a handle — and clarifies that either returned identifier is acceptable, removing the main ambiguity an agent would hit. It offers no explicit 'when not to use' or named alternative (e.g., versus bernstein_status or bernstein_subscribe).

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools