Pronounce / pronounce-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| pronounceA | Look up the canonical pronunciation of a developer-related word. Returns the IPA, a respelling that approximates how engineers actually
say the word, a playable MP3 |
| search_pronunciationsA | Search the dictionary by partial word or category match. Matches substrings against the entry's Returns a list of matching entries with |
| list_pronunciationsA | List dictionary entries, optionally filtered by category. Categories include: product, project, cli-tool, tool, cs-term,
acronym, abbreviation, person. The dictionary holds well over 1500
entries and grows continuously, so the unfiltered list is large —
pass |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| browse_index | The full dictionary index (URL → human-readable browse page). |
TDQS
Scored across 3 tools
Each tool has a clearly distinct purpose: pronounce for exact word lookup, search_pronunciations for partial/category matching, and list_pronunciations for browsing with filters. The only slight overlap between search and list is clarified by their descriptions.
Two tools follow a verb_noun pattern (search_pronunciations, list_pronunciations), while the core tool is just the bare verb pronounce. This is a minor deviation, but the overall naming is predictable and readable.
Three tools is well-scoped for a pronunciation dictionary: lookup, search, and list cover the essential interaction modes without redundancy. Each tool earns its place.
For the stated domain of looking up developer-related pronunciations, the surfaces are complete: exact lookup, discovery by partial match, and category-based browsing. There are no obvious dead ends or missing operations.