Skip to main content
Glama
Sign In

Tera Studio

by co.terastudio
OverviewDiscussionsAdmin

Get own-voice song instructions

get_own_voice_song_instructions
Read-onlyIdempotent

Explain how to hear a song sung in the person's own voice with Tera Studio, and give them the link to start. They create an account on terastudio.co, sing for about a minute, add a song they have the rights to use, and hear it back in their voice. Use it when someone wants to hear themselves sing a song, make a cover in their own voice, or turn a song into a gift in their voice. It returns steps and a link and creates nothing. Tera Studio only uses the person's own voice: not for celebrity or other people's voices.

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

Input Schema

NameRequiredDescriptionDefault
languageNoThe language the song is sung in, if they said.
occasionNoWhat it's for, if they said: a birthday, a wedding, a gift.
song_titleNoThe song they want to hear in their voice, if they named one.

Output Schema

NameRequiredDescriptionDefault
stepsYes
consentYes
start_songYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive, but the description adds real context the annotations cannot convey: the end-to-end flow (create terastudio.co account, sing ~1 minute, add a rights-cleared song, hear it back), that it returns steps plus a link, and that it creates nothing. The own-voice-only restriction is a meaningful behavioral constraint. Only the exact shape of the returned steps is left to the output schema.

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?

Front-loaded with what the tool does and what it returns, then usage triggers, then the safety constraint. Slightly repetitive about 'their own voice,' but every sentence carries new information and there is no filler.

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?

With an output schema covering the return value and annotations covering safety, the description supplies everything else an agent needs: the user journey, the rights requirement, the created-nothing guarantee, and the own-voice-only restriction. Nothing material to correct invocation is missing.

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?

Schema description coverage is 100%, so each of the three optional parameters (language, occasion, song_title) is already documented in the schema with its purpose and 'if they said' semantics. The description adds no syntax or usage detail beyond that, so the baseline 3 applies.

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?

States a specific verb-and-resource: explain how to hear a song in the person's own voice with Tera Studio and hand back the link to start. Siblings (find_song_key, find_song_key_and_tempo, shift_song_key) operate on key/tempo rather than service onboarding, so the domains are cleanly separate even though no sibling is named directly.

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?

Gives explicit triggers -- 'when someone wants to hear themselves sing a song, make a cover in their own voice, or turn a song into a gift in their voice' -- and an explicit exclusion: not for celebrity or other people's voices. Both the when and the when-not are stated in the text.

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

All Tera Studio toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources