Symbioza

List your jobs

listJobs

Read-onlyIdempotent

List the jobs THIS account has submitted, newest first — the tool to reach for when you do not have an executionId in hand (a fresh session, a lost id, "what am I still running?"). Each row carries executionId, submittedAtMs, the spec's image, budgetUsd, status, stage, artifactsReady, the same nextAction hint getStatus returns, and its deliveryOutcome, priceUsd and priceStatus; call getStatus for the full detail of any one of them. Returns count (rows served) and totalCount (jobs you have) — when they differ the list was truncated to the newest limit. Free, books nothing, and scoped: it never returns a job another account submitted.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`limit`	No	How many of the newest jobs to return. Default 20, maximum 100; out-of-range values are clamped, never rejected.
`authKey`	No	Usually omit this. The customer door — the OAuth-signed-in HTTPS connector at https://symbioza.dev/mcp — authenticates the session itself, so no key is passed per call. Only a self-hosted or test transport passes a key here.

Output Schema

TableJSON Schema

Name	Required	Description
`code`	No	Machine-readable refusal code: unauthorized, invalid_spec, budget_too_low, insufficient_balance, access_required, secret_conflict, no_compute, unavailable, refused
`jobs`	No	This account's jobs, newest first
`count`	No
`action`	No	The one next step: authenticate, fix_spec, raise_budget, add_funds, claim_credit, add_access, relax_spec_or_retry, retry_later, contact_support
`reason`	No	Why, in a customer-safe sentence
`rejected`	No	Present and true when the call was refused; nothing was booked or charged
`totalCount`	No	All of this account's jobs; larger than count when the list is truncated
`supportedImages`	No	On an unverified-image refusal: the images the door accepts

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedOct 7, 2026

addedOutput schema / properties / jobs / items / properties / executedAttempt

Added value: +{
+  "anyOf": [
+    {
+      "additionalProperties": {},
+      "properties": {
+        "exitCode": {
+          "anyOf": [
+            {
+              "type": "number"
+            },
+            {
+              "type": "null"
+            }
+          ]
+        },
+        "exitedAtMs": {
+          "anyOf": [
+            {
+              "type": "number"
+            },
+            {
+              "type": "null"
+            }
+          ]
+        },
+        "index": {
+          "type": "number"
+        },
+        "startedAtMs": {
+          "anyOf": [
+            {
+              "type": "number"
+            },
+            {
+              "type": "null"
+            }
+          ]
+        }
+      },
+      "required": [
+        "index",
+        "exitCode",
+        "startedAtMs",
+        "exitedAtMs"
+      ],
+      "type": "object"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "description": "The attempt that ran your command (0-based); null when no attempt ran it"
+}

addedOutput schema / properties / jobs / items / properties / exitCode

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

addedOutput schema / properties / jobs / items / properties / recoveryAssessment

Added value: +{
+  "anyOf": [
+    {
+      "additionalProperties": {},
+      "properties": {
+        "automatic": {
+          "type": "boolean"
+        },
+        "blocker": {
+          "anyOf": [
+            {
+              "type": "string"
+            },
+            {
+              "type": "null"
+            }
+          ],
+          "description": "dependency_access | constraint | budget | capacity | checkpoint | cleanup_unconfirmed | unknown; null unless blocked"
+        },
+        "mode": {
+          "description": "none | resume | restart | blocked | user_stopped",
+          "type": "string"
+        },
+        "needsNewApproval": {
+          "type": "boolean"
+        },
+        "nextAction": {
+          "type": "string"
+        },
+        "preserved": {
+          "additionalProperties": {},
+          "properties": {
+            "checkpoint": {
+              "type": "boolean"
+            },
+            "files": {
+              "type": "number"
+            },
+            "verifiedFiles": {
+              "type": "number"
+            }
+          },
+          "required": [
+            "files",
+            "verifiedFiles",
+            "checkpoint"
+          ],
+          "type": "object"
+        },
+        "reason": {
+          "type": "string"
+        }
+      },
+      "required": [
+        "mode",
+        "blocker",
+        "reason",
+        "nextAction",
+        "preserved",
+        "needsNewApproval",
+        "automatic"
+      ],
+      "type": "object"
+    },
+    {
+      "type": "null"
+    }
+  ]
+}

Changed2 schema fields changedSep 30, 2026

changedOutput schema / properties / action / description

Previous value: -"The one next step: authenticate, fix_spec, raise_budget, add_funds, claim_credit, relax_spec_or_retry, retry_later, contact_support"New value: +"The one next step: authenticate, fix_spec, raise_budget, add_funds, claim_credit, add_access, relax_spec_or_retry, retry_later, contact_support"

changedOutput schema / properties / code / description

Previous value: -"Machine-readable refusal code: unauthorized, invalid_spec, budget_too_low, insufficient_balance, no_compute, unavailable, refused"New value: +"Machine-readable refusal code: unauthorized, invalid_spec, budget_too_low, insufficient_balance, access_required, secret_conflict, no_compute, unavailable, refused"

First observedSep 29, 2026

TDQS

A4.9/5.0

Behavior5/5

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

Annotations already cover readOnly/idempotent/non-destructive, and the description adds genuinely new behavior: it is free and books nothing, it is account-scoped so it never returns another account's job, and it discloses truncation semantics (count vs totalCount diverging means the list was clipped to newest limit). That is real context beyond the structured hints.

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?

A single dense paragraph that front-loads purpose, then use-case, then return shape, then cost/scope caveats. Every clause carries information and it ends on the two guarantees an agent most needs (free, account-scoped); no filler.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

An output schema exists and the description still enumerates the row fields plus count/totalCount, so the agent knows both the invocation contract and the shape of results. For a read-only listing tool with annotations and an output schema, nothing material is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so limit and authKey are already documented (including clamping). The description nonetheless ties limit to observable behavior by explaining that count/totalCount divergence means truncation to the newest `limit`, adding meaning above the schema's baseline.

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 verb+resource+scope: jobs THIS account submitted, newest first. It explicitly contrasts itself with getStatus ("call getStatus for the full detail of any one of them") and with the sibling family by naming executionId as the alternative entry point.

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 the exact triggering conditions ("when you do not have an executionId in hand — a fresh session, a lost id, 'what am I still running?'") and routes to the alternative (getStatus) for per-job detail. Nothing 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 Symbioza tools Inspect

Try in Browser

Shareable, User-Owned Context BackendPeople, applications, and agents read, write, and coordinate together in one context lake. Reach it over MCP, a CLI, a Python SDK, or REST.fulcradynamics.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.