Elysia Tools Docs
EN
Language
ZHESPTRUFRDEEN
Back to site
Browse tools

Media

Emergency Alert Intelligibility Simulator

Test whether an alert retains heuristic speech clarity after bandwidth, compression, and noise degradation.

file· File resultOpen tool

Quick start

Call this tool from your code in three languages.

cURL
# 1) Request a presigned URL → returns { uploadUrl, storageKey }
curl -X POST 'https://api.elysiatools.com/api/upload/presign/audio-emergency-alert-intelligibility' \
  -H 'Content-Type: application/json' \
  -d '{"filename":"audioFile.ext","contentType":"application/octet-stream","size":12345}'

# 2) PUT the file bytes directly to the presigned uploadUrl
curl -X PUT '<presigned uploadUrl>' \
  --data-binary @/path/to/file.ext

# 3) Call the tool, passing the returned storageKey for each file field
curl -X POST 'https://api.elysiatools.com/en/api/tools/audio-emergency-alert-intelligibility' \
  -F 'audioFile=uploads/2026/01/01/your-tool-1700000000000-abc123.ext' \
  -F 'simulation=moderate' \
  -F 'minimumRetainedPercent=70' \
  -F 'outputFormat=wav'

© 2026 Elysia Tools. Developer documentation.

Back to siteBrowse tools

API reference

Send a POST request with your inputs as JSON. File parameters require a separate upload first.

Endpoint

HTTP
POST https://api.elysiatools.com/en/api/tools/audio-emergency-alert-intelligibility

Parameters

NameTypeRequiredDescription
audioFilefileupload requiredYes—
simulationselectNo—
minimumRetainedPercentnumberNo—
outputFormatselectNo—
File-type parameters must be uploaded first via POST /upload/audio-emergency-alert-intelligibility, then the returned filePath is passed to the corresponding file field.

Response format

File result

JSON
{
  "filePath": "/public/processing/randomid.ext",
  "fileName": "output.ext",
  "contentType": "application/octet-stream",
  "size": 1024,
  "metadata": {
    "key": "value"
  },
  "error": "Error message (optional)",
  "message": "Notification message (optional)"
}

MCP integration

Add this tool to your Model Context Protocol server so AI agents can list and call it.

Server configuration

Add this block to your MCP client configuration:

mcp.json
{
  "mcpServers": {
    "elysiatools-audio-emergency-alert-intelligibility": {
      "name": "audio-emergency-alert-intelligibility",
      "description": "Test whether an alert retains heuristic speech clarity after bandwidth, compression, and noise degradation.",
      "baseUrl": "https://api.elysiatools.com/mcp/sse?toolId=audio-emergency-alert-intelligibility",
      "command": "",
      "args": [],
      "env": {},
      "isActive": true,
      "type": "sse"
    }
  }
}

List available tools

After connecting to the SSE endpoint, list the exposed tools:

tools/list
{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/list"
}

Call this tool

Invoke the tool by its id, passing arguments built from its parameters:

tools/call
{
  "jsonrpc": "2.0",
  "id": 2,
  "method": "tools/call",
  "params": {
    "name": "audio-emergency-alert-intelligibility",
    "arguments": {
  "audioFile": "https://example.com/file.ext",
  "simulation": "moderate",
  "minimumRetainedPercent": 70,
  "outputFormat": "wav"
}
  }
}
Chain multiple tools in one session with a comma-separated toolId list, e.g. /mcp/sse?toolId=png-to-webp,jpg-to-webp,gif-to-webp (max 20).
File parameters accept a public file URL only (https://…). Local paths, data: URIs, and Base64 strings are not supported.

Questions or issues? Contact [email protected]

Browse tools
Open tool