Skip to main content
Glama
Sign In

AI SENSE Free Public Tools

by com.aisenseapi
OverviewDiscussionsAdmin

Spell text as sound

spell_audio
Read-onlyIdempotent

Spell text as a spoken WAV: one recorded clip per letter a to z and digit 0 to 9, the words dash and underscore for those two characters, a pause for a run of whitespace (or the spoken word space with space word), other characters skipped and listed. Letter case is marked with the words upper and lower at every change when the text mixes cases (case auto), always (on) or never (off). Two voices: kristin (default) and cori, generated once from voices trained on public-domain speech. speed 0.5 to 2 in steps of 0.1 stretches the sound with its pitch kept. Through MCP the text is at most 64 characters, since the audio comes back inline; REST takes 256. Nothing is stored. No API key, no account and no sign up.

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": {
      "text": "<text>"
    },
    "name": "spell_audio"
  }
}

Input Schema

NameRequiredDescriptionDefault
caseNoauto by default: upper and lower are spoken at each case change only when the text mixes cases.
textYesThe text to spell, 1 to 64 characters; letters, digits, dashes, underscores and spaces are spoken.
spaceNopause by default: a run of whitespace is a 0.4 second pause; word speaks the word space instead.
speedNo1 by default: 0.5 is half speed and 2 double, in steps of 0.1; the pitch stays.
voiceNokristin by default.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / speed
      Added value: +{
+  "description": "1 by default: 0.5 is half speed and 2 double, in steps of 0.1; the pitch stays.",
+  "maximum": 2,
+  "minimum": 0.5,
+  "type": "number"
+}
  2. Added

TDQS

A4.1/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint and closed-world behavior, so the safety profile is covered. The description adds real value beyond them — 'Nothing is stored,' no API key/account, output returned inline, and the 64-character MCP cap — but it never says what the inline payload concretely looks like (base64, MIME type, size) or where skipped characters are 'listed,' which is the one behavior an agent could get wrong.

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?

It is front-loaded with the core action and every clause carries information — no filler. The main structural flaw is that it is delivered as one long comma-spliced sentence, so parameter details (case, space, speed, voice) are not visually separable; the trailing 'no API key, no account, no sign up' is mild redundancy with the earlier 'Nothing is stored.'

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 5-parameter tool with full schema coverage, no output schema, and annotations covering safety, the description covers the essentials: input limits, character handling, voice options, and the no-storage guarantee. The gap is the response shape — with no output schema, an agent still does not know the return payload's encoding or where unspoken characters are surfaced.

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 description coverage is 100%, so the 3 baseline applies; the description goes further by explaining that a run of whitespace becomes a pause, that unknown characters are skipped and listed, and that case words are emitted at each change. The speed note that pitch is preserved and the voice provenance add meaning the enum-only schema does not carry.

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?

Opens with a specific verb and resource plus the output format: 'Spell text as a spoken WAV,' then immediately enumerates the mapping (one clip per letter/digit, 'dash'/'underscore' for those characters, pause for whitespace). This is unmistakably distinct from sibling audio tools like encode_audio or decode_audio, since it converts text into synthesized speech rather than transcoding.

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?

The description gives strong operational context for choosing and sizing a call — inline audio means 64 characters via MCP versus 256 via REST, and no key or account is needed. It does not name an alternative tool or state a when-not-to-use condition, so it falls short of a 5.

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 toolsInspect
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.

Resources