aziel-runtime

Register a local hash receipt

mesh_broadcast

Record a SHA-256 hash receipt for a local file without uploading or publishing its contents. Provide the 64-character hex digest plus optional title or product labels, and use confirm=true to write or dry_run=true to preview.

Instructions

Register the SHA-256 of a local file as a hash receipt — never a publish or upload path. Use this when the operator already holds a local file and wants only its hash recorded. Do not use it for uploading bytes, publishing video, sending mail, or joining a mesh node; use local qnm-node/ anon-broadcast loopback, AZMail via fraggate_call, or mesh_join instead. Write: stores a hash receipt only. Does NOT accept video bytes. Operator keeps the file. Malformed sha256 refuses MESH-BAD-INPUT; publish-shaped keys refuse MESH-NO-PUBLISH. sha256 is required (64 hex). title and product are optional labels, not file contents. Mutation requires confirm=true (runtime gate) or dry_run=true (preview only, no write). confirm and dry_run stay optional on inputSchema.required. Returns hash receipt (sha256, optional title).

Input Schema

TableJSON Schema

Name	Required	Description
`title`	No	Optional short title for the receipt. Not the file contents.
`sha256`	Yes	Required 64-character hex SHA-256 of the local file. Hash receipt only — not a publish path.
`confirm`	No	Documented confirmation flag. Optional in inputSchema.required (connector refresh must not break). tools/call still refuses MCP-CONFIRM-REQUIRED when confirm is missing or false unless dry_run=true (preview, no write).
`dry_run`	No	Optional preview flag. When true, return a would-mutate preview and do not write. Alternative to confirm=true. Does not mutate.
`product`	No	Optional catalog product slug to attribute the receipt. Not required.

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.

Changed3 schema fields changedv2.0.2Sep 18, 2026

changedInput schema / description

Previous value: -"sha256 is required (64 hex). This is a receipt, not a blob upload."New value: +"sha256 is required (64 hex). This is a receipt, not a blob upload. Mutation requires confirm=true or dry_run=true."

addedInput schema / properties / confirm

Added value: +{
+  "description": "Documented confirmation flag. Optional in inputSchema.required (connector refresh must not break). tools/call still refuses MCP-CONFIRM-REQUIRED when confirm is missing or false unless dry_run=true (preview, no write).",
+  "type": "boolean"
+}

addedInput schema / properties / dry_run

Added value: +{
+  "description": "Optional preview flag. When true, return a would-mutate preview and do not write. Alternative to confirm=true. Does not mutate.",
+  "type": "boolean"
+}

Addedv1.6.2Sep 12, 2026

TDQS

A4.8/5.0

Behavior5/5

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

Annotations only declare flags (readOnlyHint=false, etc.) without behavioral detail. The description supplies rich context: it stores a hash receipt only, does not accept video bytes, keeps the file with the operator, and has distinct refusal codes (MESH-BAD-INPUT, MESH-NO-PUBLISH). It also explains the mutation gate (confirm=true or dry_run=true) and that dry_run never writes, going well beyond 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.

Conciseness4/5

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

The description is dense and front-loaded with the core purpose, but it is long. Most sentences contribute unique information—exclusions, error behavior, and gating semantics—so the length is justified for a tool with nontrivial safety constraints. Slight redundancy with schema text (e.g., parameter labels) prevents a 5.

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 5-parameter schema, 100% schema coverage, output schema, and the complexity of mutation gating, the description covers every behavioral corner an agent needs: what happens on invalid input, publish-shaped keys, dry-run behavior, and explicit alternatives. Nothing required for correct invocation 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 the schema already documents each parameter. The description adds meaningful meta-semantics beyond the schema: sha256 is required and 64 hex, title and product are 'labels, not file contents,' and confirm/dry_run are intentionally optional in inputSchema.required yet enforce a runtime mutation gate. This exceeds the baseline while not being strictly necessary.

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: 'Register the SHA-256 of a local file as a hash receipt' and immediately clarifies 'never a publish or upload path.' It clearly distinguishes this tool from publishing, uploading, mailing, and mesh joining, matching the title 'Register a local hash receipt.'

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?

The description gives an explicit when-to-use condition: 'Use this when the operator already holds a local file and wants only its hash recorded.' It then lists what not to use it for and names concrete alternatives: 'use local qnm-node/ anon-broadcast loopback, AZMail via fraggate_call, or mesh_join instead.' This is complete routing guidance with no ambiguity.

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