Aziel Runtime

Library papers and cites

library_lookup

Read-onlyIdempotent

Search the Aziel Digital Library for papers and cites (aziel-corpus search, example, or skill) — cites, not beliefs and not vault stamps. Use this when you need a library paper, cite, example record, or library skill after Softwares and fraggate_call. Do not use it for running a Softwares slug, adaptive memory belief, ChainLock facts, or private-file search; use fraggate_call for a catalog slug, memory_recall, or chainlock_recall instead. Not a private-file search engine and not AKM/ChainLock. Empty q does not invent a cite. Unknown ops refuse FG-UNKNOWN-OP (allowed: search, example, skill, health). Named corpus wrapper — not MASTER-33; full aziel-corpus LIVE_OPS stay on fraggate_call. q is public corpus text — not memory_recall q and not ChainLock q. Omit op to search. Extra keys besides q/op/payload ride along as aziel-corpus payload (same as passing payload{}). Returns search, example, skill, or health payload inside the display envelope.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`q`	No	Optional public-corpus query for op=search. Empty q returns an empty or default hit set, not an invented cite. Not a memory or ChainLock query.
`op`	No	Optional library verb. search (default) looks up public corpus text; example returns a sample; skill returns the library skill; health is liveness. Other values refuse FG-UNKNOWN-OP.

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 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."

First observedSep 24, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive), and the description adds genuinely new behavior: unknown ops refuse with FG-UNKNOWN-OP, empty q does not invent a cite, and extra keys are forwarded as corpus payload. It stops short of describing pagination, result limits, or auth requirements, so not a full 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?

Purpose and routing are front-loaded, which is good, but the description is a dense run-on that repeats the same exclusions twice ('not beliefs and not vault stamps' then 'not a private-file search engine and not AKM/ChainLock') and re-lists the op enum. Several clauses do not earn their place.

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 spelled out, and the description still notes the display-envelope wrapping. Routing, error behavior, and default op are all covered; only minor gaps like limits or auth context remain for this low-complexity, zero-required-param tool.

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 100% and the schema already documents q, the op enum, the default, and the empty-q behavior, so the description is largely restating structured data. The only marginal addition is clarifying that extra keys ride along as payload — which the schema description already states. Baseline 3 is correct.

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 ('Search the Aziel Digital Library for papers and cites') and immediately draws boundaries against siblings by declaring what it is NOT (beliefs, vault stamps, private-file search). An agent can distinguish it from fraggate_call, memory_recall, and chainlock_recall 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?

Explicitly names the triggering context ('when you need a library paper, cite, example record, or library skill after Softwares and fraggate_call') and enumerates the negative cases with the exact alternative to use for each ('use fraggate_call for a catalog slug, memory_recall, or chainlock_recall instead'). This is a full when/when-not/alternative routing table.

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.