Delta Signal

render_signature

Render a Delta Signal audio signature (WAV, 48 kHz) that hides your message: in the heartbeat rhythm, as text in the spectrogram, as an inaudible watermark, and optionally as an SSTV picture, a ggwave data chirp or modem tones. Returns a download link (kept 7 days) and a manifest. Survives YouTube-grade AAC/Opus.

Input Schema

Name	Required	Description
`seed`	No	Watermark key; keep it to verify later
`layers`	No	Per-layer options: bed, heartbeat, primes, glyph {band: mid\|hi}, watermark {payload}
`preset`	No	Named preset: expands to a layer + sting bundle. Explicit options override the preset.
`stings`	No
`message`	Yes	Printable ASCII, up to 32 characters
`duration`	No	Seconds of signature body (default 60)

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedNov 1, 2026

addedInput schema / properties / preset

Added value: +{
+  "description": "Named preset: expands to a layer + sting bundle. Explicit options override the preset.",
+  "enum": [
+    "maddie",
+    "dax",
+    "skippy",
+    "cp"
+  ],
+  "type": "string"
+}

First observedOct 28, 2026

TDQS

A4/5.0

Behavior5/5

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

Beyond the annotations, the description discloses key behavior: output is 48 kHz WAV, the message is hidden in heartbeat/spectrogram/watermark layers, optional SSTV/ggwave/modem stings exist, a download link is retained 7 days, and a manifest is returned. It also states the output survives YouTube-grade AAC/Opus, which is important operational context not covered by annotations.

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

Conciseness5/5

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

The description is three front-loaded sentences: purpose first, then capabilities, then return and durability behavior. Every sentence contributes useful information without repetition or filler.

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 six-parameter tool with nested layer/sting objects and no output schema, the description covers the core output contract, retention, format, robustness, and high-level layer behavior. It leaves preset names, nested layer/sting details, and the seed-verification workflow to the schema, which is acceptable but not fully complete.

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 description coverage is high at 83%, so the schema already carries most parameter meaning. The description adds conceptual context by mapping message hiding to heartbeat rhythm, spectrogram text, watermark, and optional SSTV/ggwave/modem tones, but it does not add precise semantics for seed, preset, layers, stings, or duration beyond the schema.

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?

The description states a specific verb and resource: render a Delta Signal audio signature as a WAV. It makes the generative nature clear and distinguishes it implicitly from decode/verify siblings, but it never explicitly names or contrasts those alternatives.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is implied: this is the tool for creating hidden-message audio signatures. However, there is no explicit when-to-use guidance, no exclusions, and no mention of when to use decode_audio or verify_signature instead.

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

All Delta Signal 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.

Resources

Need Help?