Skip to main content
Glama
Sign In
mcp-server-sensory

mcp-server-sensory

by jaspertvdm
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

sstv_detect

Analyze base64-encoded WAV audio to detect the presence of an SSTV signal, initiating the REFLUX decoding process.

Instructions

Detect if audio contains an SSTV signal. First step of REFLUX decode.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "audio_base64": "<audio_base64>"
    },
    "name": "sstv_detect"
  }
}

Input Schema

NameRequiredDescriptionDefault
audio_base64YesBase64 encoded WAV audio

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.1

TDQS

B3.4/5.0
Behavior2/5

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

No annotations are provided, so the description fully bears the burden. It states detection of an SSTV signal but does not describe what the tool returns (e.g., boolean, confidence), side effects, or prerequisites, leaving behavior ambiguous.

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 extremely concise (two sentences) and front-loaded with the core purpose, containing no superfluous information.

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

Completeness2/5

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

The tool lacks an output schema and the description omits any indication of return value or result format. Given its simple detection purpose, it should at least hint at the output type (e.g., yes/no) to be 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?

The schema has 100% coverage for the single parameter audio_base64, already describing it as 'Base64 encoded WAV audio'. The description adds no additional semantic value beyond what the schema provides.

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 verb 'Detect' and the resource 'SSTV signal in audio', and distinguishes itself from sibling tools like reflux_decode by positioning as the first step.

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?

The description notes it is the 'First step of REFLUX decode', implying a sequential use, but does not explicitly state when to use versus alternatives or provide exclusion criteria.

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

Deploy Server

Other Tools