Overview
Word Pronunciation works by analyzing the word provided and getting the pronunciation. It uses advanced algorithms to get the pronunciation of the word and returns the pronunciation.
The tool
Once your client is connected to the VerveKit server, this appears in its tool list as WordPronunciationSkill. It is read-only and open-world — it fetches and never mutates anything on your side — so most clients call it without asking you to confirm.
{
"name": "WordPronunciationSkill",
"arguments": {
"word": "hello"
}
}You do not name the tool yourself; the model picks it. Asking about hello in the terms this skill covers is enough for it to reach for WordPronunciationSkill on its own — naming it explicitly also works, and is the way to force the call.
Connecting
One server URL covers every skill in the catalog, including this one. Authorization is OAuth: the client opens a browser once, and there is no key to paste into a config file.
{
"mcpServers": {
"vervekit": {
"url": "https://api.vervekit.com/v1/mcp"
}
}
}https://api.vervekit.com/v1/mcpPer-client setup — Claude, Cursor, VS Code, ChatGPT — is on the MCP setup page.
Arguments
These are the properties on the tool's inputSchema, so a well-behaved client validates them before the call is made. Premium arguments are accepted on every plan but only take effect on plans that include them.
| Argument | Type | Description |
|---|---|---|
wordRequired | string | The word to get the pronunciation of |
What the model gets back
The result carries a structuredContent object matching the tool's declared outputSchema, so a client reads fields without parsing prose. status is "ok" and error is null on success; a null field means the value was not available for that input, not that the call failed.
{
"status": "ok",
"error": null,
"data": {
"word": "hello",
"pronounciation": "HH AH0 L OW1"
}
}Response fields
Paths are relative to data. Premium fields are absent rather than zeroed on plans that do not include them, so check for presence instead of comparing to 0.
| Field | Type | Example | Description |
|---|---|---|---|
word | string | hello | The word provided for pronunciation lookup |
pronounciation | string | HH AH0 L OW1 | Phonetic pronunciation of the word in ARPAbet format |
Failure modes
Errors come back as tool errors carrying a sentence the model can act on, not a bare status code. Error handling covers the full list.
| Status | What it means |
|---|---|
400 / 422 | The arguments did not validate. The message names the offending one. |
401 | The OAuth session is invalid or expired — reconnect the server. |
403 | Blocked by a key restriction or an IP allow-list. Never a bad identity. |
404 | This skill is not part of VerveKit. Check the catalog. |
429 | Out of credits, or a brief rate limit. The message tells them apart. |
A call costs 2 credits each time the tool actually runs; a model that reasons about the tool without calling it costs nothing.
Use cases
- Language Learning
- Use the Word Pronunciation API to get word pronunciation for language learning. Use the data to learn correct pronunciation, improve language skills, and enhance communication
- Speech Recognition
- Get word pronunciation by using the Word Pronunciation API for speech recognition. Use the data to recognize words, transcribe speech, and enhance voice commands
- Text-to-Speech
- Use the Word Pronunciation API to get word pronunciation for text-to-speech. Use the data to convert text to speech, generate audio files, and enhance accessibility
- Pronunciation Guide
- Get word pronunciation by using the Word Pronunciation API for pronunciation guide. Use the data to create pronunciation guides, improve pronunciation, and enhance understanding
Other ways to use Word Pronunciation Skill
Set up Word Pronunciation Skill on VerveKit, or reach the same source a different way. Your VerveKit account and credits work on all of them — one key, one balance.
Related
More in Text Processing: