aziel-runtime

QNM suite rollup

mesh_status

Read-onlyIdempotent

Read QNM suite rollup totals for enabled status, bearers, public Nodes, Live Nodes, and software Worker rosters; use when you need these counts, not individual nodes or radio enablement.

Instructions

Read QNM suite rollup totals (enabled?, bearers, nodes = human mesh users + cited human uses, live_nodes = human mesh users + site_live_viewers, software_nodes = {slug}-worker roster) — not the node roster. Packet-transfer cite is QNS-CD-1.0 (photon QNS1 1.3 on local qnsd; GET /v1/qns cites only; Worker does not proxy via emit). Use this when you need public Nodes (users + uses), Live Nodes (users + site viewers), or software_nodes (product Worker roster). Do not use it for listing individual nodes, enabling extra radios, or executing a catalog engine; use mesh_nodes, mesh_enable, or fraggate_call instead. Read-only. Never enables radios beyond default suite-presence. Read-only suite-presence is ON by default. Open-world awareness bind is 0.0.0.0 beside those radios (law LIVE; Worker socket live-when-configured; not a loopback fence; not a Cap-7 public egress IP). Not a login mesh. Views/MCP/downloads do not enter QNM-S. Full node process is local qnm-node/. Kernel-direct fabric wrapper — not MASTER-33; not a second Softwares door. Softwares exec stays fraggate_call. Returns enabled flag, bearers, nodes (human mesh users + cited uses), live_nodes (human mesh users + site_live_viewers), human_mesh_users, site_live_viewers, human_uses, active_nodes, inactive_nodes, isolated_nodes, software_nodes (product Workers), and QNS-CD-1.0 cite.

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 display.action, title, and summary, then take the next input. Never echo raw tool names.
`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.

Changed5 schema fields changedv2.0.9Sep 29, 2026

changedOutput schema / description

Previous value: -"Display envelope shown to the user (display.title / display.summary) plus the machine result. Extra engine fields may appear."New value: +"Display envelope shown to the user (display.action / display.title / display.summary) plus the machine result. Extra engine fields may appear. Do not echo raw tool names."

changedOutput schema / properties / display / description

Previous value: -"Human-facing envelope. Show title and summary, then take the next input."New value: +"Human-facing envelope. Show display.action, title, and summary, then take the next input. Never echo raw tool names."

addedOutput schema / properties / display / properties / action

Added value: +{
+  "description": "Human-visible run frame. Always \"Run aziel runtime\". Product verb titles stay on title. Not a tool name.",
+  "type": "string"
+}

addedOutput schema / properties / display / properties / image

Added value: +{
+  "additionalProperties": true,
+  "description": "Present only when a real production included png_b64, jpeg_b64 (or the same byte family), or a cited http(s) image URL. No invented thumbs. Omitted on dry_run. reviewed is true only when executed production bytes are attached; a dry_run never mints reviewed.",
+  "properties": {
+    "data": {
+      "description": "Base64 image bytes copied from the production. Omitted for a URL-only cite. Never present on dry_run.",
+      "type": "string"
+    },
+    "mimeType": {
+      "description": "Sniffed image media type (image/png, image/jpeg, image/webp, or image/gif).",
+      "type": "string"
+    },
+    "reviewed": {
+      "description": "True only when data came from an executed production. False for a URL cite without bytes. Never true on dry_run.",
+      "type": "boolean"
+    },
+    "source": {
+      "description": "Production field the image was taken from (for example png_b64, jpeg_b64, or image_url).",
+      "type": "string"
+    },
+    "url": {
+      "description": "Cited http(s) image URL when the production named one. Not invented.",
+      "type": "string"
+    }
+  },
+  "type": "object"
+}

changedOutput schema / properties / display / properties / title / description

Previous value: -"Short result title for the AI client."New value: +"Product verb title for the AI client. Not a raw tool name."

Addedv1.6.2Sep 12, 2026

TDQS

A4/5.0

Behavior4/5

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

Annotations already cover readOnlyHint, idempotentHint, destructiveHint, and openWorldHint. The description adds meaningful context beyond those: 'Never enables radios beyond default suite-presence', 'Read-only suite-presence is ON by default', and network-binding caveats. Some of this is cryptically worded, but it does not contradict the annotations.

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 very long and packed with unexplained internal jargon. It is not front-loaded for quick scanning, and many clauses (e.g., 'Kernel-direct fabric wrapper — not MASTER-33; not a second Softwares door') do not clearly help an agent decide or invoke the tool.

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 complex, zero-parameter suite-rollup tool with an output schema, the description provides ample surrounding context about scope, defaults, and exclusions. It redundantly lists return fields that the output schema already covers, but overall it gives enough to call the tool correctly.

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 takes zero parameters and schema coverage is 100%, so the baseline is 4. The description adds nothing about parameters because there are none to describe, which is appropriate.

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 and resource ('Read QNM suite rollup totals') and explicitly distinguishes itself from the node roster sibling via 'not the node roster' and 'use mesh_nodes instead'. The heavy domain jargon makes it harder to parse than the ideal, but the functional purpose is clear for an agent familiar with the suite.

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?

Contains an explicit 'Use this when...' clause listing the three rollup sub-resources, and a 'Do not use it for...' clause naming the exact alternative tools (mesh_nodes, mesh_enable, fraggate_call) for each excluded case. This is as explicit as usage routing gets.

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