gaudio-developers-mcp

Official

by gaudiolab-mcp

Overview Schema Related Servers Score Discussions

TypeScript

Remote

Server Quality Checklist

Profile completionA complete profile improves this server's visibility in search results.

Latest release: v1.1.3
Disambiguation4/5
Tools are mostly distinct with clear purposes, though there is intentional overlap between granular workflow tools (upload_file/create_job/get_job) and high-level 'all-in-one' wrappers (separate_audio, sync_lyrics). Descriptions mitigate confusion by explicitly labeling the latter as all-in-one and specifying when to use each path.
Naming Consistency5/5
All tools follow a consistent gaudio_verb_noun pattern using snake_case. Verbs (create, get, list, separate, sync, upload) and nouns (job, models, audio, lyrics, file) are applied uniformly throughout the set.
Tool Count5/5
Seven tools is well-scoped for an audio processing API, providing granular primitives (upload, create, get) alongside convenience wrappers for common workflows (separation, lyrics sync), plus metadata tools (models, key info) without bloat.
Completeness4/5
Covers the full job lifecycle (upload, create, get/status) for the three model categories mentioned (stem, dme, text_sync). Minor gaps exist for operational completeness (no list_jobs, cancel_job, or delete operations), but core CRUD and domain-specific workflows are present.
Average 4.1/5 across 7 of 7 tools scored. Lowest: 3.5/5.
See the Tool Scores section below for per-tool breakdowns.
- No community issues in the last 6 months
- 1 commit in the last 12 weeks
- Last stable release on April 5, 2026
- No critical vulnerability alerts
- No high-severity vulnerability alerts
- No code scanning findings
- CI status not available
This repository is licensed under MIT License.
This repository includes a README.md file.
No tool usage detected in the last 30 days. Usage tracking helps demonstrate server value.
Tip: use the "Try in Browser" feature on the server page to seed initial usage.
This repository includes a glama.json configuration file.
If you are the author, simply .
If the server belongs to an organization, first add glama.json to the root of your repository:
```
{
  "$schema": "https://glama.ai/mcp/schemas/server.json",
  "maintainers": [
    "your-github-username"
  ]
}
```
Then . Browse examples.
Add related servers to improve discoverability.

How to sync the server with GitHub?

Servers are automatically synced at least once per day, but you can also sync manually at any time to instantly update the server profile.

To manually sync the server, click the "Sync Server" button in the MCP server admin interface.

How is the quality score calculated?

The overall quality score combines two components: Tool Definition Quality (70%) and Server Coherence (30%).

Tool Definition Quality measures how well each tool describes itself to AI agents. Every tool is scored 1–5 across six dimensions: Purpose Clarity (25%), Usage Guidelines (20%), Behavioral Transparency (20%), Parameter Semantics (15%), Conciseness & Structure (10%), and Contextual Completeness (10%). The server-level definition quality score is calculated as 60% mean TDQS + 40% minimum TDQS, so a single poorly described tool pulls the score down.

Server Coherence evaluates how well the tools work together as a set, scoring four dimensions equally: Disambiguation (can agents tell tools apart?), Naming Consistency, Tool Count Appropriateness, and Completeness (are there gaps in the tool surface?).

Tiers are derived from the overall score: A (≥3.5), B (≥3.0), C (≥2.0), D (≥1.0), F (<1.0). B and above is considered passing.

Tool Scores

Behavior3/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations provided, so the description bears full responsibility. It discloses the workflow (upload, create job, poll, return results) and constraints (size, format). However, it omits behavioral details like whether resources persist, authorization needs, or side effects. For a tool that creates jobs, this is adequate but not exhaustive.
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?
The description is a single paragraph that front-loads the purpose and then lists requirements. It is concise with no wasted words, though a bulleted list could improve readability. It earns a 4 for efficiency and clarity.
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?
Given 6 parameters, no output schema, and no annotations, the description covers the essential process, input constraints, and deliverable format (CSV + JSON report URLs). It lacks details about polling mechanics or report structure, but is substantially complete for an agent to invoke the tool.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Parameters3/5
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Input schema has 100% coverage with descriptions for all 6 parameters. The description adds workflow context (e.g., 'upload audio + text files' maps to the file path/upload ID parameters) but does not significantly extend parameter meaning beyond the schema. A baseline of 3 is appropriate.
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?
The description clearly states the tool's purpose with a specific verb+resource: 'upload audio + text files → create gts_lyrics_line_v1 job → poll → return CSV + JSON report URLs'. This distinguishes it from sibling tools like gaudio_create_job which likely only creates a job without the upload+sync workflow.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Usage Guidelines3/5
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description provides usage constraints (text format, audio limits) but lacks explicit guidance on when to use this tool versus alternatives (e.g., manually calling gaudio_upload_file and gaudio_create_job). It implies the all-in-one nature but does not state comparative benefits or exclusions.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Behavior3/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries full burden. It discloses the polling nature, status states, and URL expiration, but does not mention authentication or request limits. It is adequate but not comprehensive.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Conciseness5/5
Is the description appropriately sized, front-loaded, and free of redundancy?
Two concise sentences pack the essential information: purpose, status states, and download URL expiration. No superfluous content.
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 simple status-checking tool with two required parameters and no output schema, the description covers key aspects: status enumeration, URL expiration, and result availability. Could mention that results are included on success, but overall complete.
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?
Input schema covers both parameters with descriptions (100% coverage). The description adds value by indicating that jobId comes from specific creation tools (gaudio_create_job or gaudio_separate_audio), which is helpful context beyond 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?
The description clearly states the tool's purpose as checking job status and retrieving results, and lists possible statuses with outcomes. This distinguishes it from sibling tools like gaudio_create_job (creation) or gaudio_list_models (listing).
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Usage Guidelines3/5
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description implies usage after job creation but does not explicitly state when to use this tool versus alternatives or provide exclusions. It does include a useful note about download URL expiration.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Behavior4/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations provided, so description carries full burden. It discloses multipart upload behavior, uploadId validity (72 hours), reusability across jobs, and supported formats. This is good transparency for a file upload action.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Conciseness5/5
Is the description appropriately sized, front-loaded, and free of redundancy?
Two sentences clearly front-loading the purpose and then adding key details. Every sentence adds value without redundancy.
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?
Covers upload process, reusability, formats, and validity. However, does not explicitly state what the tool returns (e.g., uploadId). Minor gap but overall sufficient for an upload tool.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Parameters3/5
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The schema already describes filePath as 'Absolute path to the local file'. The description adds context about supported formats but does not significantly enhance parameter understanding beyond the schema. Baseline 3 is appropriate.
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?
The description clearly states it uploads a local audio/video/text file to Gaudio servers, with automatic multipart upload. This verb+resource combination is specific and distinct from sibling tools that deal with jobs, models, etc.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Usage Guidelines3/5
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description explains automatic multipart upload and uploadId reuse, but does not explicitly specify when to use this tool versus alternatives like gaudio_create_job. Usage is implied but not clearly guided.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Behavior3/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations provided, so the description carries full burden. It states the tool retrieves information, implying a safe, read-only operation, but does not disclose potential side effects (e.g., authentication requirements or rate limits). Given the tool's simplicity, this is minimally adequate but not rich.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Conciseness5/5
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single sentence that front-loads the purpose and enumerates key output fields. No wasted words; every element contributes to clarity.
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?
Given no output schema, the description fully covers return values by listing all relevant fields. With zero input parameters and a simple read operation, the description is complete and sufficient for an agent to use the tool 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?
The input schema has zero parameters, so the description need not explain them. It adds value by listing the returned fields, helping the agent understand what the tool provides. Baseline is 4 for no parameters.
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?
The description clearly identifies the tool's action ('Get') and the resource ('API key information'), listing specific attributes (description, creation date, status, etc.). It distinguishes itself from sibling tools like gaudio_create_job and gaudio_separate_audio, which handle different operations.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Usage Guidelines3/5
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description implies a simple read operation but lacks explicit guidance on when to use this tool versus alternatives. No exclusions or prerequisites are mentioned, though the context of sibling tools suggests it's for retrieving key metadata.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Behavior3/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the burden. It mentions listing and filtering but does not disclose read-only nature, authentication, or rate limits. The behavior is implied but not explicit.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Conciseness5/5
Is the description appropriately sized, front-loaded, and free of redundancy?
A single, front-loaded sentence that efficiently conveys purpose and parameter usage with no wasted words.
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?
Given low complexity (one optional parameter, no output schema), the description adequately covers purpose and filtering. It does not explain output format, but this is acceptable for a simple list tool.
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% with descriptions for each enum value. The description adds real-world meaning ('stem' = instrument separation) beyond the schema, aiding selection.
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?
The description clearly states the tool lists Gaudio AI models and explains the filter categories. The verb 'list' and resource 'models' are precise, and it distinguishes from sibling tools like gaudio_create_job or gaudio_separate_audio.
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 implies usage for viewing models by category but lacks explicit when-to-use or when-not-to-use guidance. However, the context of sibling tools provides clarity on distinct purposes.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Behavior3/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description must disclose behavior. It explains the multi-step workflow and the polling interval parameter. However, it does not mention potential side effects, rate limits, error handling, or what happens on failure. The polling behavior is partially described but lacks details on completion criteria.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Conciseness5/5
Is the description appropriately sized, front-loaded, and free of redundancy?
Two sentences, front-loaded with the core purpose, followed by targeted details. No redundant or extraneous information. Every sentence adds value.
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 description covers the full workflow, input parameters, and output (download URLs). It lists supported file formats and differentiates between modes. Without an output schema, it provides enough context for basic usage, though it could include more detail on result structure or error scenarios.
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%, and the description adds context: it clarifies that filePath and uploadId are alternatives, explains the conditional use of 'type' for Stem Separation, and notes the default pollInterval. This goes beyond the schema's individual parameter descriptions.
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?
Description clearly states the tool's purpose as an all-in-one audio separation workflow (upload, create job, poll, download). It distinguishes between Stem Separation and DME Separation modes and lists supported file types, making it highly specific and distinct from siblings.
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?
Provides clear guidance on when to provide 'type' for Stem Separation and that DME Separation doesn't need it. Also explains upload options (filePath vs uploadId). However, it does not explicitly address when NOT to use this tool or compare it to sibling tools like gaudio_create_job or gaudio_upload_file.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Behavior4/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Given no annotations, the description discloses key behavioral traits: the conditional requirement of the 'type' parameter based on model selection. It does not mention potential side effects, authentication needs, or error cases, but the provided information is sufficient for safe usage.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Conciseness5/5
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is concise with three sentences, each serving a purpose: stating the action, explaining parameter rules for different models, and providing an alternative tool. No extraneous information.
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?
With three parameters, no output schema, and no annotations, the description adequately explains parameter usage and conditional logic. It could optionally mention the output (e.g., job ID), but the current information is sufficient for the agent to invoke the tool 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 baseline is 3. The description adds value by explaining the conditional requirement of the 'type' parameter and providing examples (e.g., 'vocal', 'vocal,drum,bass'), which go beyond the schema's description.
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?
The description clearly states 'Create a processing job with an uploaded file', identifying the specific verb and resource. It distinguishes from sibling tools by mentioning that for Text Sync, one should use gaudio_sync_lyrics instead.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Usage Guidelines5/5
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description provides explicit guidance on when to use this tool: for Stem Separation models, the 'type' parameter is required; for DME models, no type is needed; and for Text Sync, a different tool is recommended. This effectively tells the agent when to use and when not to use the tool.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

GitHub Badge

Glama performs regular codebase and documentation scans to:

Confirm that the MCP server is working as expected.
Confirm that there are no obvious security issues.
Evaluate tool definition quality.

Our badge communicates server capabilities, safety, and installation instructions.

Card Badge

Copy to your README.md:

[![gaudio-developers-mcp MCP server](https://glama.ai/mcp/servers/gaudiolab-mcp/gaudio-developers-mcp/badges/card.svg)](https://glama.ai/mcp/servers/gaudiolab-mcp/gaudio-developers-mcp)

Score Badge

Copy to your README.md:

[![gaudio-developers-mcp MCP server](https://glama.ai/mcp/servers/gaudiolab-mcp/gaudio-developers-mcp/badges/score.svg)](https://glama.ai/mcp/servers/gaudiolab-mcp/gaudio-developers-mcp)

Latest Blog Posts

Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)
By Om-Shree-0709 on July 25, 2026.
mcp
Agent Identity
OAuth 2.1
Your AI Chatbot Just Exposed Your CEO's Salary to an Intern
By Om-Shree-0709 on July 2, 2026.
Agent Identity
MCP Security
OAuth Delegation
Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)
By Om-Shree-0709 on June 30, 2026.
Agentic Ai
Prompt Injection
WebAssembly

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/gaudiolab-mcp/gaudio-developers-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server