Skip to main content
Glama

Agent Data Tools: Full list (every tool as its own definition)

Voice agent: spoken question in, spoken answer out, with memory

voice_agent
Read-only

One turn of a voice assistant: send the user's voice note (or text), your instructions and the earlier turns; get back what was heard, a short reply, the reply spoken in English, Spanish, French, Chinese, Japanese or Korean and the updated history to send next time. Speech up to 2 minutes (MP3/WAV, or 1 MB of other formats); replies up to 600 characters. Use for voice bots in Telegram or WhatsApp, phone menus, kiosks and hands-free helpers. Example: text=What time do you open on Saturday?. Price $0.05/call via x402 USDC or a card key (/credits); failed calls free. Reads or computes only and changes nothing; each call is charged, so repeats are not free.

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

Input Schema

NameRequiredDescriptionDefault
urlNoAbsolute http(s) URL of the user's spoken turn (MP3/WAV up to 2 minutes, other formats up to 1 MB); or POST the file; or send text instead
langNoReply language and voice: en, es (Aura-2 MP3), fr, zh, ja or ko (MeloTTS WAV); default en
textNoThe user's turn as text (or send audio with url or a POSTed file)
voiceNoAura-2 voice for an en or es reply (default luna for en, aquila for es); fr, zh, ja and ko have one voice each
historyNoEarlier turns as a JSON array of {role, content}, as returned in history by the last call
instructionsNoWho the assistant is and what it knows (up to 2,000 characters)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior5/5

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

Beyond the annotations, it discloses the actual operational envelope: 2-minute audio cap, 1 MB cap for other formats, 600-character reply cap, per-call pricing ($0.05 via x402 USDC or card key), and that failed calls are free. It also explains why idempotentHint=false matters in practice — every call is billed, so repeats are not free — and restates the read-only, no-side-effect nature, which is unusually complete cost/limit disclosure.

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 core one-turn contract is front-loaded in the first sentence, with limits, use cases, example and pricing following in a logical order and no filler. It is dense — pricing and format caps sit in the same block as the semantics — but every sentence carries a distinct, actionable fact.

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 no output schema, the description must describe the return value, and it does: what was heard, a short reply, the spoken reply in the chosen language, and updated history for the next call. Combined with the format ceilings and billing note, an agent has everything needed to call this correctly on the first try.

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 coverage is 100%, so the media constraints, language enum, voice defaults and 2,000-character instruction limit are already fully documented in the schema. The description adds only the round-trip meaning of `history` ('the updated history to send next time'), which the schema largely covers already; 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 states a concrete verb and resource set: one turn of a voice assistant taking audio or text plus instructions/history and returning transcript, reply text, synthesized speech and updated history. That input/output shape (audio in, audio plus memory out) is specific enough to separate it from pure transcription or pure text-to-speech siblings without needing to name them.

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 names concrete deployment contexts (Telegram/WhatsApp bots, phone menus, kiosks, hands-free helpers) and gives a worked example, so an agent knows the intended situation. It stops short of explicit exclusions or directing single-purpose needs (a one-off transcript or a one-off TTS clip) to a sibling, so it is clear context without full routing rules.

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.