Skip to main content
Glama

Verify a pronunciation

pronunciations_verify

[writes flayr data · write scope] Speaks a carrier sentence with the entry in a voice (default Gemini Puck), transcribes it, and passes when the transcript has the term or an accepted hearing. CHARGES EMBERS per check: only call it when the user asks, after telling them the price (GET /api/v2/pronunciations/{id}/verify quotes it; nothing is charged for a quote). Never refunded, even when the check fails or cannot run. id from pronunciations_list. (Wraps POST /api/v2/pronunciations/{id}/verify.)

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": {
      "id": "<id>"
    },
    "name": "pronunciations_verify"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesPronunciation id (GET /api/v2/pronunciations).
modelNo
voiceNo
brandIdNoBrand id, or `personal`.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.8/5.0
Behavior5/5

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

Goes well past the annotations: discloses the `write` scope, the ember charge per check, that charges are never refunded even on failure, and that quoting is free. It also explains the pass condition, so the agent knows what a successful outcome means before spending user credits.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with the write/scope tag and the cost warning before the mechanics; every clause carries distinct information (cost, irreversibility, quote path, id source). Dense but no redundant sentences.

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?

For a 4-param, no-output-schema mutation-with-cost tool, the description covers cost, irreversibility, required scope, pass criteria, and where to get the id. Only the `model` and `brandId` parameters lack any explanation anywhere in the definition.

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?

Adds real meaning for `voice` by naming the default (Gemini Puck) and points `id` at pronunciations_list, both beyond the terse schema text. With 50% schema coverage, `model` and `brandId` remain unexplained in either place, which keeps it short of a 5.

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?

States a concrete multi-step action: speaks a carrier sentence in a voice, transcribes it, and passes when the transcript matches the term or an accepted hearing. The wrapped endpoint (POST /api/v2/pronunciations/{id}/verify) and the `id` source (pronunciations_list) make it unmistakable versus siblings like pronunciations_upsert or pronunciations_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?

Explicit gating: 'only call it when the user asks, after telling them the price,' plus a named alternative (the quote GET endpoint) for price discovery at no charge. That is a full when-to-use / when-not-to-use / alternative structure.

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.

Resources