Aziel Runtime

First call — pick a Softwares slug

Softwares

Read-onlyIdempotent

Read the Softwares catalog and pick a slug (first call). Not the hashed live/stub registry. Use this when an agent starts, or a hub refreshes the Software tab, and a slug is needed before fraggate_call. Do not use it for executing that slug, hashed live/stub discovery, or library papers; use fraggate_call after the slug is picked, fraggate_list for hashes, or library_lookup for papers instead. Empty {} only. Never enables mesh radios and never execs. tools/list name is Softwares. runtime_software is a tools/call alias and is not a second listed tool. Same JSON as GET /v1/software (also /v1/fraggate/software). Cards carry name, slug, ops, worker_home — not live/stub/digest hashes. EmbryoLock is live-with-local-destructive-boundary (worker_home embryolock-download-tracker). Plain A–Z → Gate A–Z → Lock A–Z (Clock ≠ Lock), including AZChat LIVE+bound. After this catalog, pick a slug and call fraggate_call. library_lookup is for library papers and cites. Returns sorted software cards (name, slug, ops, worker_home) matching GET /v1/software.

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	Software-tab catalog JSON (products/cards with name, slug, ops, worker_home, sort lanes Plain→Gate→Lock). Not a hashed registry roster.
`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.

Changed1 schema field changedSep 28, 2026

changedInput schema / description

Previous value: -"No arguments. Send {}. Hub/client helper — not exec and not fraggate_list."New value: +"No arguments. Send {}. First call — pick a slug, then fraggate_call. Not exec and not fraggate_list."

Changed5 schema fields changedSep 27, 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."

AddedSep 26, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive/openWorld=false, yet the description adds real value: 'Never enables mesh radios and never execs', the tools/call alias mapping (runtime_software), and the exact card fields returned. It does not cover pagination or rate/limit behavior, so it stops short of a 5.

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

Conciseness3/5

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

The first sentence front-loads the purpose well, but the body is padded: the slug-then-fraggate_call instruction is stated twice, and cryptic fragments ('Plain A–Z → Gate A–Z → Lock A–Z (Clock ≠ Lock)', 'EmbryoLock is live-with-local-destructive-boundary') add length without clear operational payoff.

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 explained, yet the description still summarizes card contents and the REST equivalence. Usage, aliases, and safety are all covered; only the opaque acronym-chain content slightly muddies an otherwise complete picture.

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?

Zero parameters with 100% schema coverage, so the baseline is 4; the description reinforces 'Empty {} only.', which matches the schema and removes any ambiguity about sending arguments.

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 and resource ('Read the Softwares catalog and pick a slug (first call)') and explicitly separates itself from the 'hashed live/stub registry'. It names the sibling tools it is not (fraggate_call, fraggate_list, library_lookup), so an agent can route without opening any 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 ('when an agent starts, or a hub refreshes the Software tab, and a slug is needed before fraggate_call'), explicit when-not ('Do not use it for executing that slug, hashed live/stub discovery, or library papers') and names each alternative with its condition.

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

All Aziel Runtime tools Inspect

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.