SSTV Decoder

decode_sstv

Demodulate a presented slow-scan-television (SSTV) audio recording, anchor the audio fingerprint and the decoded image hash to the Knox event chain, and return a self-authenticating receipt bundle (Knox anchor + C2PA-aligned envelope + FRE 902(13)/(14)-shape affidavit). Audio bytes are NOT retained — only the SHA-256 fingerprint and the decoded image are anchored. Bonis Systems does not capture audio on its own; the audio must be presented by the caller (a public WebSDR recording, a customer-controlled SDR capture they consent to submit, or audio they own). Phase 1 supports Martin M1 (VIS code 0x2C, 320×256 RGB). Other VIS codes return mode = 'unsupported' with detected hex. Requires a Knox Bearer API key on the Authorization header — unauthenticated calls are rejected.

Input Schema

TableJSON Schema

Name	Required	Description
`name`	Yes	Display name for the recording (max 256 chars).
`capture`	No	Optional capture-context metadata.
`sampleRate`	No	Required when audioFormat = 'pcm16-mono'.
`audioBase64`	Yes	Base64-encoded audio. Either a complete WAV file (RIFF/WAVE, 8/16/24-bit PCM or 32-bit IEEE float, mono or stereo, 4-192 kHz) or raw 16-bit signed little-endian mono PCM samples.
`audioFormat`	No	Audio container ('wav' default, or 'pcm16-mono').

TDQS

A4/5.0

Behavior4/5

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

Discloses that audio bytes are not retained, only fingerprints anchored, and that unauthenticated calls are rejected. Also notes unsupported modes return an 'unsupported' status. Annotations absent, so description carries burden well.

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?

Description is informative but slightly dense; front-loaded with key action. Every sentence adds value, but some technical details could be streamlined.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Covers audio format, supported mode, anchoring, and auth, but lacks details on the output receipt bundle structure. No output schema, so description should clarify output fields more.

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%, so baseline 3. Description adds context about anchoring behavior and auth requirements but does not significantly expand on parameter meanings beyond the schema.

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 clearly states the tool's action: demodulate SSTV audio, anchor fingerprints, and return a receipt bundle. It distinguishes from the sibling tool 'verify_sstv_decode' by focusing on decoding versus verification.

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

Usage Guidelines4/5

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

Provides context on when to use: supports Martin M1 only, audio must be provided by caller, requires authentication. Lacks explicit when-not-to-use or alternatives beyond the sibling tool's name hint.

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

All SSTV Decoder tools Inspect

Try in Browser

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.4/5.0

Disambiguation5/5

Each tool has a distinct purpose: decode_sstv performs decoding and anchoring, while verify_sstv_decode handles verification. No functional overlap exists.

Naming Consistency5/5

Both tool names follow the consistent verb_noun pattern (decode_sstv, verify_sstv_decode) using snake_case.

Tool Count5/5

With only 2 tools, the server is tightly scoped to its core functionality: decoding and verifying SSTV audio. This is appropriate for a specialized server.

Completeness5/5

The tool set covers the complete lifecycle presented: decoding and anchoring, followed by verification. No obvious gaps for the stated domain.

Resources

Need Help?