Skip to main content
Glama

converse

Record your speech to get a transcript and English feedback on pronunciation, grammar, and fluency. Use for voice conversations with coaching.

Instructions

Record the user speaking, transcribe it, and return the transcript plus quick English feedback. This is the primary tool for voice conversations: call it, read the transcript + feedback, then respond conversationally in your own words — weaving the feedback in naturally or mentioning it only if it matters.

Recording auto-stops when the user finishes speaking (silence detection).

Use this tool when:

  • The user wants to chat with you by voice instead of typing

  • The user wants casual English feedback while talking with you

  • You want to hear what the user said rather than read a typed message

For a focused drill where the user reads a specific sentence, use practice instead.

Args: target_hint: Optional. Only set this if the user is explicitly trying to say a specific sentence (e.g. they asked "how do I say X?" and you told them X). Leave blank for free-form conversation. duration: Maximum recording duration in seconds (default 30, max 120). Auto-stops earlier on silence.

Returns: Markdown report containing the user's transcript, brief English feedback (pronunciation + grammar + fluency), and a 'For Claude' section with guidance on how to respond.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
target_hintNo
durationNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior4/5

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

Although no annotations exist, the description explains key behaviors: auto-stop on silence, duration limits (default 30, max 120), and the components of the return value. It does not mention privacy or authentication, but for a recording tool this is sufficient.

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 well-structured with a summary, auto-stop note, usage list, and parameter details. It is slightly verbose but every sentence serves a purpose; no fluff.

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 the presence of an output schema, the description adds value by explaining the return content (transcript, feedback, guidance) and usage context. It covers the tool's role among siblings adequately, though it could detail edge cases like long silences.

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

Parameters5/5

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

With 0% schema description coverage, the description fully compensates by explaining both parameters: target_hint (optional, for specific sentences) and duration (default 30, max 120, auto-stop). This adds significant meaning beyond the raw 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 records user speech, transcribes it, and returns transcript plus English feedback. It distinguishes itself from the sibling 'practice' tool for focused drills, making the purpose unambiguous.

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 explicitly lists when to use this tool (voice chats, casual feedback) and when to use an alternative (use 'practice' for focused drills). This provides clear guidance on tool selection.

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

Install Server

Other Tools

Latest Blog Posts

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/JuhongPark/mcp-server-pronunciation'

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