aziel-runtime

Step 1 — List the FragGate registry

fraggate_list

Read-onlyIdempotent

List the hashed FragGate registry to discover catalog names and slugs. Use when you don't yet know the identifier; returns entries, allowlists, and digests.

Instructions

List the hashed FragGate registry (live / stub / local_only + digests) so you can discover names. Discovery first — not a hub Software tab and not exec. Use this when you do not yet know the catalog name or slug. Do not use it for hub Software-tab refresh, inspecting one known capability, or executing an op; use Softwares (GET /v1/software), fraggate_describe, or fraggate_call instead. Empty {} only. Never enables mesh radios. Never invents tools or ops. Compact LIVE_OPS tokens below are discovery hints required by product verify scripts — they are not exec. Call fraggate_describe for the live card; later unknown names refuse FG-HALLUC-TOOL. Returns registry entries, allowlists, digests, and the MASTER-33 pipeline cite. Not the full FragGate door. Empty fraggate_list is discovery (hashed LIVE_OPS). Catalog LIVE_OPS slugs (40): 4dmap, ark, azai, azbot, azbrowser, azchat, azclce, azcoherence, azhub, aziel-corpus, azieltether, azinterface, azmail, aznet, azos, azvpn, chronolock, codelock, decisiongate, embryolock, employeelock, foldlock, forgereceipts, glossafilter, godlock, mialock, miragegrid, mmconsensus, peacelock, postking, shadowlock, spectrallock, staticclock, temporallock, toolbench, trajectorylock, vibelock, whistlelock, zkattest, zsolver. Compact product-verify tokens (not a second allowlist): allowlist.azhub LIVE_OPS: health, skill, region_list, place_module, remove_module, tether_declare, tether_cut, tether_list, blank_key_status, list_modules, place. allowlist.azinterface LIVE_OPS: health, skill, genesis_status, site_state_get, site_state_set, integrity_check, witness_list, page_cycle_status, genesis_boot, hold. allowlist.azbrowser LIVE_OPS: ethical_search, lamb_lens_search, navigate, airlock_ingest, airlock, home, tab_open, tab_list, receipt_list, verify, receipt_verify, sandbox_status, sandbox_render, health, skill, vpn. allowlist.azvpn LIVE_OPS: health, skill, doctor, limitation, describe, open, status, list, close, send, recv, pull, peers, attach. allowlist.aznet LIVE_OPS: health, doctor, pair_status, pair, garden_list, stamp, verify_hash, memorial_list, memorial_append, receipt_verify, skill. UI aliases forward to catalog ops. EmbryoLock LIVE_OPS health/skill/doctor/verify-hash/policy/limitation; wipe/scorch/unlock stay FG-STUB on the public mesh.

Input Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Output Schema

TableJSON Schema

Name	Required	Description
`code`	No	FragGate or fabric code when present: FG-OK, FG-HALLUC-TOOL, FG-STUB, FG-LOCAL-ONLY, FG-UNKNOWN-OP, FG-GATE-REFUSE, FG-LAMB-REFUSE, or a module refuse such as MESH-* / AKM-*.
`door`	No	Door name. The public door is fraggate.
`ran_in`	No	Execution locale (for example aziel-runtime) when present.
`result`	No	FragGate body: ok, code, door, slug, op, engine_digest, ran_in, provenance, refusal, limitations, receipt, plus the engine result. Unknown names refuse FG-HALLUC-TOOL; stubs refuse FG-STUB.
`status`	No	HTTP-like status when present on wrappers (200 ok; 400+ error / refuse).
`display`	No	Human-facing envelope. Show title and summary, then take the next input.
`receipt`	No	Optional receipt, ledger tip, or TemporalLock/ForgeReceipts exit when the door stamped one.
`refusal`	No	Explicit refuse object, code, or message when the door or engine refused.
`engine_op`	No	Resolved engine op when present (often inside result).
`ledger_tip`	No	Ask/refuse ledger tip when the door stamped one.
`provenance`	No	Provenance / input packet when the pipeline attached one.
`session_id`	No	Raw session id when session plumbing was used. Hidden unless the user asked for the chain.
`engine_slug`	No	Resolved engine slug when present (often inside result).
`limitations`	No	Capability limitations or Remain-OFF notes when present.
`engine_digest`	No	64-hex engine_digest when a true in-process engine ran (often inside result).

Schema Changelog

Changes observed during successful MCP inspections.

Changed4 schema fields changedv1.6.2Sep 12, 2026

changedInput schema / additionalProperties
```
Previous value: -trueNew value: +false
```

addedInput schema / description

Added value: +"No arguments. Send {}. Discovery first — not describe or execute."

addedInput schema / properties
```
Added value: +{}
```

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "additionalProperties": true,
+  "description": "Display envelope shown to the user (display.title / display.summary) plus the machine result. Extra engine fields may appear.",
+  "properties": {
+    "code": {
+      "description": "FragGate or fabric code when present: FG-OK, FG-HALLUC-TOOL, FG-STUB, FG-LOCAL-ONLY, FG-UNKNOWN-OP, FG-GATE-REFUSE, FG-LAMB-REFUSE, or a module refuse such as MESH-* / AKM-*.",
+      "type": "string"
+    },
+    "display": {
+      "additionalProperties": true,
+      "description": "Human-facing envelope. Show title and summary, then take the next input.",
+      "properties": {
+        "fields": {
+          "description": "Optional labeled scalars copied from the result for display.",
+          "items": {
+            "additionalProperties": true,
+            "properties": {
+              "label": {
+                "description": "Field label.",
+                "type": "string"
+              },
+              "value": {
+                "description": "Field value as text.",
+                "type": "string"
+              }
+            },
+            "type": "object"
+          },
+          "type": "array"
+        },
+        "next": {
+          "description": "What the agent should do after showing this output.",
+          "type": "string"
+        },
+        "summary": {
+          "description": "One-line outcome or refuse reason.",
+          "type": "string"
+        },
+        "title": {
+          "description": "Short result title for the AI client.",
+          "type": "string"
+        }
+      },
+      "type": "object"
+    },
+    "door": {
+      "description": "Door name. The public door is fraggate.",
+      "type": "string"
+    },
+    "engine_digest": {
+      "description": "64-hex engine_digest when a true in-process engine ran (often inside result).",
+      "type": "string"
+    },
+    "engine_op": {
+      "description": "Resolved engine op when present (often inside result).",
+      "type": "string"
+    },
+    "engine_slug": {
+      "description": "Resolved engine slug when present (often inside result).",
+      "type": "string"
+    },
+    "ledger_tip": {
+      "description": "Ask/refuse ledger tip when the door stamped one."
+    },
+    "limitations": {
+      "description": "Capability limitations or Remain-OFF notes when present."
+    },
+    "provenance": {
+      "description": "Provenance / input packet when the pipeline attached one."
+    },
+    "ran_in": {
+      "description": "Execution locale (for example aziel-runtime) when present.",
+      "type": "string"
+    },
+    "receipt": {
+      "description": "Optional receipt, ledger tip, or TemporalLock/ForgeReceipts exit when the door stamped one."
+    },
+    "refusal": {
+      "description": "Explicit refuse object, code, or message when the door or engine refused."
+    },
+    "result": {
+      "description": "FragGate body: ok, code, door, slug, op, engine_digest, ran_in, provenance, refusal, limitations, receipt, plus the engine result. Unknown names refuse FG-HALLUC-TOOL; stubs refuse FG-STUB."
+    },
+    "session_id": {
+      "description": "Raw session id when session plumbing was used. Hidden unless the user asked for the chain.",
+      "type": "string"
+    },
+    "status": {
+      "description": "HTTP-like status when present on wrappers (200 ok; 400+ error / refuse).",
+      "type": "integer"
+    }
+  },
+  "type": "object"
+}

AddedSep 5, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false. The description adds useful non-obvious behavior: 'Never enables mesh radios. Never invents tools or ops' and clarifies that compact tokens are 'not exec' and that unknown names 'refuse FG-HALLUC-TOOL'. This goes beyond the annotations without contradicting them.

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

Conciseness2/5

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

The description is massively over-sized for a zero-parameter list tool. The opening sentence is front-loaded and clear, but the subsequent 40-item catalog slug list and per-module allowlist dumps are reference material that belongs in the tool output or schema, not the description. Several phrases are repeated ('discovery', 'not exec') and add little for tool selection.

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?

Given the tool has no parameters, an output schema exists, and annotations cover side effects, the description leaves no selection gap: it states what is returned, what is not returned ('Not the full FragGate door'), when to call fraggate_describe instead, and how to interpret the embedded tokens. It is more than complete, though completeness is achieved at the cost of conciseness.

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?

The tool has zero parameters and schema coverage is 100%, so the baseline is 4. The description reinforces the empty-object contract ('Empty {} only') and explains that discovery is its sole action, which is slightly more than the schema's 'No arguments. Send {}.'

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 opens with a specific verb and resource: 'List the hashed FragGate registry (live / stub / local_only + digests) so you can discover names.' It also explicitly distinguishes itself from siblings ('not a hub Software tab and not exec', 'use Softwares, fraggate_describe, or fraggate_call instead'), so an agent can differentiate it without inspecting schemas.

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 gives explicit when-to-use ('Use this when you do not yet know the catalog name or slug'), when-not-to-use ('Do not use it for hub Software-tab refresh, inspecting one known capability, or executing an op'), and names the alternative tools for each case. It even clarifies that the embedded LIVE_OPS tokens are discovery hints, not execution commands.

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