Skip to main content
Glama

Axad

Voice

show_voice
Read-only

Plays a line or short dialogue for the learner to listen to, with the transcript hidden until shown or answered. It can limit replays like an exam's listening part, ask one question, or serve as repeat-after-me practice.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "lines": "<lines>",
      "lang": "<lang>"
    },
    "name": "show_voice"
  }
}

Input Schema

NameRequiredDescriptionDefault
foldNotrue: a secondary widget of this reply, made now and shown folded: only its title row, until one click opens it. Omit it on the reply's main widgets, which show open.
langYesBCP 47 code of the language the widget teaches: "nl". The view speaks and saves its words in it.
nextNoUp to 3 one-tap next steps shown under the widget: label is the button's text, ask the message a tap sends.
linesYes
playsNo
speedNo
titleNo
shadowNo
questionNo
transcriptNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / next
      Added value: +{
      +  "description": "Up to 3 one-tap next steps shown under the widget: label is the button's text, ask the message a tap sends.",
      +  "items": {
      +    "properties": {
      +      "ask": {
      +        "description": "The message a tap sends, in the learner's words.",
      +        "maxLength": 300,
      +        "type": "string"
      +      },
      +      "label": {
      +        "description": "The button's text.",
      +        "maxLength": 32,
      +        "type": "string"
      +      }
      +    },
      +    "required": [
      +      "label",
      +      "ask"
      +    ],
      +    "type": "object"
      +  },
      +  "maxItems": 3,
      +  "type": "array"
      +}
  2. First observed

TDQS

B3.1/5.0
Behavior3/5

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

Annotations already establish readOnlyHint=true, destructiveHint=false and openWorldHint=false, so safety is covered. The description adds genuinely new behavior: the transcript stays hidden until shown or answered, and replays can be capped as in an exam. It says nothing about the widget being interactive/stateful or what the learner sees after answering.

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?

Two sentences, front-loaded with the core action and its most surprising trait (hidden transcript). The second sentence is a slightly list-like run of modes but every clause carries information; no filler.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

A nested-schema tool with 10 parameters, an enum, and no output schema needs far more than a purpose statement. The description never explains the interaction model (how 'shadow', 'transcript', 'question', and the 'next' buttons combine) or the role of the required 'lines' structure, so an agent could easily misconfigure it.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

With 10 parameters and only 30% schema description coverage, the description carries a heavy burden and does not meet it: plays, speed, title, shadow, transcript, the line object's by/say/mean, and the question object are never explained. At best the mention of replay limiting and a question hints at 'plays' and 'question', which is implicit mapping rather than added meaning.

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?

The description uses a specific verb and resource ('Plays a line or short dialogue for the learner to listen to') and adds distinguishing traits such as the hidden transcript and replay limiting. It stops short of naming overlapping siblings like show_dialogue or show_shadow, so an agent must infer the boundary itself.

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?

Three usage situations are sketched (exam-style replay limiting, a single comprehension question, repeat-after-me practice), which implies when to reach for this tool. However, there is no explicit 'use X instead when' guidance despite close siblings such as show_dialogue and show_shadow, leaving the choice to inference.

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.