Skip to main content
Glama

List pronunciations

pronunciations_list
Read-onlyIdempotent

[read-only] How every flayr voice (chat voice, voiceovers, character VO) says a brand's words: pronunciations (term → sayAs respelling, with verified when a Verify passed), suggested (learned suggestions, inert until accepted) and builtIn entries. Captions and transcripts keep the written word. brandId from list_brands, or personal. (Wraps GET /api/v2/pronunciations.)

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

Input Schema

NameRequiredDescriptionDefault
brandIdNoBrand id, or `personal`. Default: a bound key's brand, else your active brand.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so the safety profile is covered. The description still adds real behavioral context beyond them: `suggested` entries are 'learned suggestions, inert until accepted', and 'Captions and transcripts keep the written word', which tells the agent pronunciations do not rewrite transcript text. It does not mention pagination or entry limits.

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 return shape, then the caption/transcript caveat, then the brandId sourcing hint and endpoint wrapper. Dense but every clause carries information; the parenthetical endpoint note is the only low-value tail.

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?

One optional parameter, no output schema, and low complexity — the description compensates by describing the returned groupings and the non-effect on captions. Missing only whether results are scoped per-voice or aggregated, which is partially covered by 'every flayr voice'.

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 100%, so the baseline is 3, but the description adds information the schema lacks: it names `list_brands` as the upstream source for `brandId` and restates the `personal` option. That resolution path is material for a model that has to obtain a valid brandId before calling.

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 states concretely what the tool returns — pronunciation entries split into `pronunciations` (term → sayAs respelling), `suggested`, and `builtIn` — and tags itself [read-only], which separates it from the mutating siblings `pronunciations_upsert` and `pronunciations_verify`. The explicit verb 'list' lives only in the title rather than the prose, so an agent must infer the retrieval action from context.

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?

Usage is implied rather than stated: the [read-only] tag and the presence of upsert/verify siblings make the read path inferable, and the description gives the sourcing hint '`brandId` from list_brands, or `personal`'. It never explicitly says when to call this versus `pronunciations_verify` (e.g., after a verify) or how to act on `suggested` entries.

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