Skip to main content
Glama

List the free NiceVois audio tools

list_free_audio_tools
Read-only

Use this to see NiceVois's free audio tools, which need no account, no API key and no sign-up: split a song into vocals and instrumental (vocal remover, acapella, karaoke instrumental), split lead vocals from backing vocals, remove background noise, remove reverb or echo, and enhance a phone-recorded or noisy vocal (Vocal Enhancer). Returns each tool's id, the accepted formats, and a website link to give the user when you cannot upload their file yourself.

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": "list_free_audio_tools"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
priceYes
toolsYes
serviceYes
workflowYes
inputFormatsYes
noFileAccessYes
maxAudioBytesYes
outputFormatsYes
accountRequiredYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / properties / accountRequired / const
      Previous value: -trueNew value: +false
  2. Changed1 schema field changed
    • changedOutput schema / properties / accountRequired / const
      Previous value: -falseNew value: +true
  3. Changed1 schema field changed
    • removedOutput schema / properties / price / const
      Removed value: -"free"
  4. Added

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds genuinely new behavioral facts beyond that: no account, no API key and no sign-up are required, and it explains the handoff behavior (give the user a website link when you cannot upload on their behalf). Return-field detail overlaps the existing output schema, which is the only redundancy.

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?

Content is front-loaded with the purpose and then the enumeration of tool types, with zero filler sentences. It is a single very long sentence, however, and the five-way capability list could be tightened without losing meaning.

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?

The tool is simple, parameterless, read-only, and already has an output schema, so the description only needs to establish what the listing is and why to call it, which it does. A brief pointer to the sibling that consumes these tool ids would have closed the last gap.

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?

There are zero parameters, so the baseline is 4; the description correctly adds nothing parameter-related. It does not confuse the agent by hinting at filters or options that do not exist.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description opens with a specific verb and resource ('see NiceVois's free audio tools') and enumerates the concrete capabilities behind each tool (vocal/instrumental splitting, backing-vocal isolation, noise removal, de-reverb, vocal enhancement). It does not name the sibling it hands off to (create_free_audio_job), so an agent must infer that this is the discovery step rather than the execution step.

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?

It gives clear usage context: this is a pre-flight lookup, and the returned website link is the fallback 'when you cannot upload their file yourself'. That implies the boundary with the job-creation siblings, but no alternative tool is named explicitly and there is no statement of when not to call this.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources