Skip to main content
Glama
MCP Fish Server

MCP Fish Server

by AceDataCloud

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
ACEDATACLOUD_API_TOKENYesYour AceDataCloud API token

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{
  "listChanged": false
}
prompts
{
  "listChanged": false
}
resources
{
  "subscribe": false,
  "listChanged": false
}
experimental
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
fish_generate_audioB

Generate speech audio from text using Fish TTS.

Use this when:
- You want to convert text to speech
- You need AI-generated audio narration

Returns:
    JSON response containing task_id and audio data when complete.

Example:
    fish_generate_audio(
        text="Hello, welcome to our service!",
        reference_id="d7900c21663f485ab63ebdb7e5905036"
    )
fish_get_usage_guideA

Get a comprehensive guide for using the Fish TTS tools.

Provides detailed information on how to use the Fish tools effectively,
including parameters, examples, and best practices.

Returns:
    Complete usage guide for Fish TTS tools.
fish_list_modelsC

List Fish voices; has_more is boolean for self=true, otherwise possibly null.

fish_get_modelA

Get a Fish voice model by ID.

Returns:
    JSON response from /fish/model/{id}.
fish_create_modelA

Save a cloned voice long-term and publicly; other users may discover and use it.

Use only reference audio authorized for processing and publication as a
reusable voice. There is no private/unlisted option. For one-shot reference
conditioning without saving a reusable model, use fish_generate_audio.
A successful create returns HTTP 201 and a voice _id; pass that _id as
reference_id to fish_generate_audio. Do not retry an uncertain create blindly.
fish_get_taskA

Query the status and result of a Fish audio generation task.

Use this to check if a task is complete and retrieve the resulting audio URL.

Task states:
- 'pending': Task is queued — keep polling
- 'processing': Task is being processed — keep polling
- 'complete': Task finished successfully
- 'failed': Task failed (check error message)

Returns:
    Task status and result data including audio URL.
fish_get_tasks_batchA

Query the status of multiple Fish tasks at once.

Efficiently checks the status of multiple audio generation tasks in a
single request.

Returns:
    Status and result data for all queried tasks.

Prompts

Interactive templates invoked by user choice

NameDescription
fish_guideGuide for choosing the right Fish TTS tool.
fish_workflow_examplesCommon workflow examples for Fish TTS tasks.

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

A3.7/5.0

Scored across 7 tools

Disambiguation5/5

Each tool targets a distinct resource+action: audio generation (fish_generate_audio), model lifecycle (create/get/list), task polling (single vs batch), and a documentation tool. The descriptions explicitly pre-empt the main confusion points, e.g. fish_create_model vs fish_generate_audio and fish_get_task vs fish_get_tasks_batch. An agent can select unambiguously.

Naming Consistency5/5

All seven tools use a uniform fish_<verb>_<noun> snake_case pattern (generate_audio, create_model, get_model, get_task, get_tasks_batch, get_usage_guide, list_models). Verb choices (get/create/list/generate) are used consistently with their intent.

Tool Count5/5

Seven tools is a well-scoped surface for a TTS service: generation, async task polling, and voice model management. No redundant or filler tools; each covers a distinct workflow step.

Completeness3/5

Voices can be created, fetched, and listed, but there is no delete/revoke operation for publicly saved models — a notable lifecycle gap given there is no private option. Task tracking also lacks a way to list outstanding tasks without knowing IDs in advance, forcing agents to remember task_ids.

Maintenance

ActivityActive
ResponsivenessNo issues