A
licenseNot graded
qualityC
maintenanceMultilingual dictionary server via Wikimedia REST and MediaWiki Action APIs, providing word definitions, summaries, search, etymology, and pronunciations.
15
1
MIT
kasahorow
Server Details
Bilingual dictionary lookup and translation validation for kasahorow Fellows.
If you are the author of this connector, you can claim ownership with GitHub, an HTTP challenge, or a DNS record. Claimed connector authors can inspect health checks, view analytics, and manage their listing.
- Status
- Healthy
- Last Tested
- Transport
- Streamable HTTP
- URL
TDQS
A3.8/5.0
Scored across 2 tools
Disambiguation5/5
The two tools serve clearly distinct purposes: lookup_word is a dictionary lookup, while validate_translation is a paid validation service. No overlap in functionality.
Naming Consistency5/5
Both tool names follow a consistent verb_noun pattern in snake_case: lookup_word and validate_translation.
Tool Count3/5
Only 2 tools is on the low side for a dictionary/translation service, but it may be acceptable for a niche purpose. Slightly more tools would improve coverage.
Completeness2/5
The server lacks basic features like listing supported languages, translating text, or adding words. The paid validation tool is an outlier, leaving significant gaps in a typical dictionary workflow.
Available Tools
2 toolslookup_wordAInspect
Look up a word in the kasahorow dictionary (WOAKA). fl = your language, tl = the language of the word. Returns definitions with parts of speech.
ParametersJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| fl | Yes | Your language, ISO code (e.g. 'en'). | |
| tl | Yes | The word's language, ISO code (e.g. 'ak', 'sw'). | |
| word | Yes | The word or short phrase to look up. |
TDQS
A3.7/5.0
Behavior3/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
The description indicates the tool is read-only and returns 'definitions with parts of speech'. However, since no annotations are provided, the description carries the full burden and fails to disclose potential error cases or idempotency guarantees.
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 a single, well-structured sentence that front-loads the purpose. It is brief and every phrase adds meaning, though it could be slightly expanded with usage guidance without losing conciseness.
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 absence of an output schema, the description adequately summarizes the return value. All three required parameters are covered, and the sibling tool is mentioned. It does not specify error handling or language availability, but for a straightforward lookup, the description is sufficient.
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?
The description adds value beyond the schema by explicitly defining 'fl' as 'your language' and 'tl' as 'the word's language', clarifying the directionality of the lookup. The schema already provides ISO code examples, but the description resolves ambiguity.
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's purpose: looking up a word in the kasahorow dictionary. It specifies the dictionary name (WOAKA) and distinguishes from the sibling tool 'validate_translation' by focusing on lookup rather than validation.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Usage Guidelines2/5
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description provides no guidance on when to use this tool versus alternatives. It does not mention when not to use it or any prerequisites for using the dictionary (e.g., language availability or internet connection).
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
validate_translationAInspect
Validate a translation with nabanya, the Connection Validator: it confirms your words transmit their feelings in the reader's language. It never rewrites your words. This is a PAID reading (N1 $15, N2 $10, N3 $5, N4 $3): the reply gives you the payment link and your report link. When the payment clears, the reading is prepared and sent to your report link and email.
ParametersJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| reader | Yes | The reader's language, ISO code (e.g. 'sw'). | |
| source | Yes | Your original writing. For N4, the single word instead. | |
| writer | Yes | The writer's language, ISO code (e.g. 'en'). | |
| product | No | Which reading. N1 ($15) validates a finished pair and needs a translation. N4 ($3) validates ONE word: put the word in `source` and leave `translation` empty. Defaults to N1. | |
| translation | No | The translation to validate. N1 only. |
TDQS
A3.9/5.0
Behavior4/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description carries the full burden and does well: it discloses the paid nature, exact dollar amounts per tier, the asynchronous process (payment link first, then report link/email after payment clears), and the explicit behavior 'It never rewrites your words.' It could add details about auth or failure states, but for a paid validation service this is substantial transparency.
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 compact, front-loaded with the core purpose, and then gives essential pricing and workflow details in a few sentences. It earns its space, though phrases like 'nabanya, the Connection Validator' and 'transmit their feelings' add slight branding wordiness without harming clarity.
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 tool with no annotations and no output schema, the description covers important context: what it does, what it never does, the cost, and what the user will receive (payment link, report link, email). It lacks failure-payment or error-handling details, but for an agent deciding whether to invoke it and setting user expectations, it is largely complete.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Parameters3/5
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 100%, so the baseline is 3. The description adds pricing context for the 'product' parameter but does not add meaning beyond what the schema already provides (e.g., N4 uses source and leaves translation empty, N1 needs translation). The schema itself already explains these parameter relationships, so the description contributes little extra semantic value.
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 opens with a specific verb and resource: 'Validate a translation' and names the validator 'nabanya'. It clearly distinguishes the tool from a rewrite tool by stating 'It never rewrites your words,' which separates it from related functions like lookup_word or rewriting services.
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?
The description communicates context such as being a PAID reading, the N1-N4 tier pricing, and the payment/report-link flow. However, it does not explicitly state when to choose this tool over alternatives (e.g., lookup_word) beyond implying 'validate a translation', and it provides no clear exclusions other than 'never rewrites your words,' which is more behavioral than a usage directive.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections. Dates show when Glama detected each change.
1 tool update
- Changed
validate_translation4 fields changed- added
Input schema / properties / productAdded value: +{ + "description": "Which reading. N1 ($15) validates a finished pair and needs a translation. N4 ($3) validates ONE word: put the word in `source` and leave `translation` empty. Defaults to N1.", + "enum": [ + "N1", + "N2", + "N3", + "N4" + ], + "type": "string" +} - changed
Input schema / properties / source / descriptionPrevious value: -"Your original writing."New value: +"Your original writing. For N4, the single word instead." - changed
Input schema / properties / translation / descriptionPrevious value: -"The translation to validate."New value: +"The translation to validate. N1 only." - changed
Input schema / requiredPrevious value: -[ - "source", - "translation", - "writer", - "reader" -]New value: +[ + "source", + "writer", + "reader" +]
2 tool updates
- First observed
lookup_word - First observed
validate_translation
Frequently Asked Questions
Claiming proves that you control a remote MCP connector. It does not move, proxy, or interrupt the server.
Open the connector listing, choose Claim ownership, and sign in to Glama.
Complete one verification method:
GitHub identity – fastest for official registry listings. For a namespace such as
io.github.alice/server, link the matching GitHub user, then choose Claim with GitHub. An organization namespace such asio.github.acme/serveralso needs that organization to have installed the Glama AI GitHub App and approved its permissions, because GitHub discloses organization membership only to apps it has installed. Use HTTP or DNS when it has not.HTTP challenge – works when you can deploy a public file. Generate a token, publish the exact JSON Glama shows at
/.well-known/glama.jsonon the same origin as the connector, then choose Check HTTP challenge.DNS challenge – works when you control DNS but cannot change the server. Generate a token, create the exact TXT record Glama shows, wait for it to propagate, then choose Check DNS challenge.
After verification, Glama sends a confirmation email and gives you access to listing details, thumbnails, health checks, and analytics. Keep the HTTP file or DNS record in place: Glama periodically checks it and ownership remains verified while the token is discoverable.
The HTTP ownership file has this structure:
{
"$schema": "https://glama.ai/mcp/schemas/connector.json",
"claim": "glama_claim_..."
}Claim tokens are opaque, stable, and bound to the signed-in Glama account. They contain no email address or other personal information. If Glama can no longer discover a verified HTTP or DNS token, it starts a seven-day grace period before removing claim-based access. Restore the same token during that period to keep ownership verified. Never publish an email address, Glama session token, GitHub token, or connector credential as ownership proof.
If verification fails, confirm that you copied the current token exactly. The HTTP file must be public, return valid JSON with a successful HTTP response, and stay on the connector's origin. DNS changes may need more time to propagate. A claim cannot transfer to a different origin or hostname: if the connector target changes, Glama starts the grace period and the new target must be claimed separately after the previous claim is released.
For a connector linked to the official MCP Registry, registry updates continue to replace its name, description, and URL by default. After claiming, open Manage connector and enable Use Glama listing details as the source of truth if edits made on Glama should be preserved. Categories and thumbnails are always managed on Glama; registry linkage and technical connection settings continue to sync.
Control your server's listing on Glama, including description and metadata
Access analytics and receive server usage reports
Get monitoring and health status updates for your server
Feature your server to boost visibility and reach more users
To improve your MCP server's ranking:
Claim ownership of the server listing
Complete the server profile with an accurate description and thumbnail
Provide a test profile so Glama can connect to and evaluate the server
Keep tool definitions clear and complete to earn a high Tool Definition Quality Score (TDQS)
Route real usage through the Glama Gateway; more recorded successful server uses also improve the ranking
For users:
Full audit trail – every tool call is logged with inputs and outputs for compliance and debugging
Granular tool control – enable or disable individual tools per connector to limit what your AI agents can do
Centralized credential management – store and rotate API keys and OAuth tokens in one place
Change alerts – get notified when a connector changes its schema, adds or removes tools, or updates tool definitions, so nothing breaks silently
For server owners:
Proven adoption – public usage metrics on your listing show real-world traction and build trust with prospective users
Tool-level analytics – see which tools are being used most, helping you prioritize development and documentation
Direct user feedback – users can report issues and suggest improvements through the listing, giving you a channel you would not have otherwise
The connector status is unhealthy when Glama is unable to successfully connect to the server. This can happen for several reasons:
The server is experiencing an outage
The URL of the server is wrong
Credentials required to access the server are missing or invalid
If you are the owner of this MCP connector and would like to make modifications to the listing, including providing test credentials for accessing the server, please contact support@glama.ai.
Discussions
No comments yet. Be the first to start the discussion!
Related MCP Connectors
Wiktionary MCP — multilingual dictionary via Wikimedia REST + MediaWiki Action API
- LexifyeOAuthpro.publifye
Build dictionaries & glossaries with AI: entries, senses, versions, print PDF, EPUB, web reader, RTL
Cited library on Ifá, the Orishas and Yoruba philosophy in 4 languages. Read-only; not an oracle.
Community-driven Egyptian Arabic slang dictionary with Arabic and Franco-Arabic search and lookup.
Related MCP Servers
- AlicenseAqualityAmaintenanceA local-first multilingual dictionary, thesaurus, translation, lexical-relations, semantic-neighbour, and English wordplay server for the Model Context Protocol (MCP). It operates fully offline with read-only query access and no data mutation while running.7Apache 2.0
- FlicenseNot gradedqualityDmaintenanceEnables bidirectional lookup of Mi'kmaq and English words with definitions and examples, and provides tools for learning and dictionary statistics, integrating seamlessly with AI-powered IDEs.1-
- AlicenseCqualityAmaintenanceProvides translation and language resources for Kenyan languages including Swahili, Kikuyu, and Luo, with tools for glossaries, language guides, and civic terminology.6MIT