AI SENSE Free Public Tools

Render music as sound

render_audio

Render music as a PCM16 mono WAV: notes written as for create_midi, or a MIDI file or a ProTracker module (MOD) given as file_base64 or storage_id. A small synthesizer plays the notes with an instrument family for each General MIDI program and drums on channel 10. At most 180 seconds of sound, a WAV of at most 7938044 bytes; a longer or denser song is cut and truncated says so. A WAV over 4 MiB, about 95 seconds, is kept in Storage for 24 hours and answered as storage_id and storage_url instead of inline audio. No API key, no account and no sign up.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "render_audio"
  }
}

Input Schema

Name	Required	Description
`notes`	No	The notes, as for create_midi.
`tempo`	No	Beats a minute for notes, 120 by default.
`program`	No	The General MIDI program for notes, 0 (the grand piano) by default.
`storage_id`	No	A storage_id from store_file, from a previous tool result, or from REST /storage. Objects expire 24 hours after they were stored.
`file_base64`	No	The file as standard base64, at most about 190 KB of file through MCP. For a larger file, store it with REST POST /services/v1/storage first and pass storage_id.

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 9, 2026

TDQS

A4.6/5.0

Behavior5/5

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

Annotations only declare that this is a non-read-only, non-idempotent, non-destructive, closed-world call. The description adds substantial behavior the annotations cannot convey: a built-in synthesizer with GM instrument families and channel-10 drums, hard caps of 180 seconds and 7,938,044 bytes, explicit truncation of longer/denser songs, and a 4 MiB threshold above which results are returned as storage_id/storage_url with a 24-hour expiry rather than inline audio.

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?

One dense, front-loaded paragraph: output format first, then accepted inputs, then limits/truncation, then storage fallback. Nearly every sentence carries operational information. The closing 'No API key, no account and no sign up' is mild boilerplate that doesn't help tool selection.

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?

There is no output schema, so the description must explain return values — and it does, distinguishing inline audio from the storage_id/storage_url response and its 24-hour retention. Limits, truncation semantics and input modes are all covered, leaving nothing an agent needs in order to call this correctly.

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 baseline is 3, but the description adds the mode framing that the schema itself does not encode: notes-mode vs file-mode (MIDI or ProTracker MOD supplied as file_base64 or storage_id), plus the role of 'program' in selecting a GM instrument family. It does not add format detail for 'tempo' or the note string syntax, leaving that to create_midi and 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?

States a specific verb and resource with an exact output format: 'Render music as a PCM16 mono WAV'. It also distinguishes itself from siblings by tying input to create_midi's note format and to file inputs (MIDI/MOD), so an agent can separate it from create_midi, read_midi, encode_audio or spell_audio without opening a schema.

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?

Gives clear conditional guidance for the two input modes — write notes as for create_midi, or pass an existing MIDI/MOD file via file_base64 or storage_id — and states when to prefer storage_id over base64 for larger files. It does not explicitly name a sibling (e.g., 'use create_midi if you want a .mid file instead') or state when-not to use this tool.

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

All AI SENSE Free Public Tools tools Inspect

Try in Browser

Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.