VAR2.ai

var2_record_voice

Read-only

Record the user's VOICE right in the chat (a recorder widget with Record / Stop / play back). "Let me record my voice", "record me", "I want to say it myself", "voice to voice from my recording", "change my voice" with no audio file → THIS first. The recording uploads to var2 and the widget sends its URL and length back to the chat; then call var2_voice_to_voice with it. Optionally pass the target voice (voice_id + voice_name from var2_get_voice_list) so it is carried along. Free; nothing is generated until voice-to-voice runs.

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

Input Schema

Name	Required	Description	Default
`voice_id`	No	Optional target ElevenLabs voice_id for the conversion afterwards (var2_get_voice_list).
`voice_name`	No	Optional display name of that voice.

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 8, 2026

TDQS

A4.8/5.0

Behavior5/5

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

Beyond the readOnlyHint annotation, the description discloses the widget interaction, that the recording uploads to var2, that the widget posts the URL and length back into the chat, that the call itself is free, and that nothing is generated until voice-to-voice runs. That is rich behavioral context an agent could not infer from annotations.

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 action and trigger phrases, then the follow-up flow; dense but nearly every clause carries routing or behavioral information. The trigger-phrase list is long, though each phrase targets a distinct user utterance, so most of it earns its place.

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?

There is no output schema, yet the description still explains what the widget returns (URL and length in chat) and what to do next. For a two-optional-parameter tool, nothing an agent needs to invoke it correctly is missing.

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 already 100%, so the baseline is 3, but the description adds purpose beyond the schema: the voice_id/voice_name are optional and are 'carried along' to the later conversion, and are sourced from var2_get_voice_list.

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 states a specific verb and resource — 'Record the user's VOICE right in the chat (a recorder widget with Record / Stop / play back)' — which is unmistakable and distinct from siblings like var2_voice_to_voice or var2_get_voice_list.

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?

It gives explicit trigger phrases ('record me', 'I want to say it myself', 'change my voice' with no audio file → THIS first) and states the follow-up step: call var2_voice_to_voice with the returned URL. It also names the voice-list sibling as the source of the optional target voice.

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

All VAR2.ai tools Inspect

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

Need Help?