Skip to main content
Glama
Sign In

main

by dev.lingo
OverviewDiscussionsAdmin

Server Details

Lingo.dev MCP Server - World-class i18n implementation with ICU MessageFormat.

The last two health checks of this connector failed. If this server requires authentication, missing or expired test credentials may be the cause. A test profile lets Glama authenticate for health checks and discover tools; it is separate from your personal connections.

If you are the author, claim ownership, then add or update a test profile under Admin → Test Profile.

Status
Unhealthy
Uptime
77.5% over 82 days
OAuth
Works in Glama
Last Tested
Transport
Streamable HTTP
URL
ChatGPT
–
Claude
–

TDQS

A4.4/5.0

Scored across 4 tools

Disambiguation5/5

Each tool has a clearly distinct purpose: i18n_checklist orchestrates the workflow, get_project_context detects project setup, get_framework_docs fetches framework docs, and get_i18n_library_docs fetches library docs. Even though the two doc tools share a similar interface, their targets are explicitly different (framework vs library), and the checklist directs which to use when.

Naming Consistency4/5

Three tools follow the get_<object>_docs/context pattern, and i18n_checklist is a noun-style name. All are lowercase snake_case and descriptive, so the minor deviation from a strict verb_noun pattern is not confusing. The i18n_ prefix on the checklist also ties it to the server's domain.

Tool Count5/5

Four tools is well-scoped for a focused i18n implementation workflow. The checklist is the central orchestrator, with three supporting tools that each serve a necessary sub-task (context detection, framework docs, library docs). No tool feels redundant or missing.

Completeness5/5

The tool surface fully covers the i18n implementation lifecycle: i18n_checklist provides the step-by-step process, get_project_context gathers the required initial context, and the two doc tools supply current reference material. The checklist's evidence submission and build validation handle verification, so there are no obvious gaps or dead ends.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

  1. 4 tool updates
    • Changedget_framework_docs3 fields changed
      • removedInput schema / additionalProperties
        Removed value: -false
      • addedInput schema / properties / context
        Added value: +{
+  "description": "Explain why you are calling this tool and how it fits into the user's overall goal. This parameter is used for analytics and user intent tracking. YOU MUST provide 15-25 words (count carefully). NEVER use first person ('I', 'we', 'you') - maintain third-person perspective. NEVER include sensitive information such as credentials, passwords, or personal data. Example (20 words): \"Searching across the organization's repositories to find all open issues related to performance complaints and latency issues for team prioritization.\"",
+  "type": "string"
+}
      • changedInput schema / required
        Previous value: -[
-  "framework"
-]New value: +[
+  "framework",
+  "context"
+]
    • Changedget_i18n_library_docs3 fields changed
      • removedInput schema / additionalProperties
        Removed value: -false
      • addedInput schema / properties / context
        Added value: +{
+  "description": "Explain why you are calling this tool and how it fits into the user's overall goal. This parameter is used for analytics and user intent tracking. YOU MUST provide 15-25 words (count carefully). NEVER use first person ('I', 'we', 'you') - maintain third-person perspective. NEVER include sensitive information such as credentials, passwords, or personal data. Example (20 words): \"Searching across the organization's repositories to find all open issues related to performance complaints and latency issues for team prioritization.\"",
+  "type": "string"
+}
      • changedInput schema / required
        Previous value: -[
-  "library"
-]New value: +[
+  "library",
+  "context"
+]
    • Changedget_project_context3 fields changed
      • removedInput schema / additionalProperties
        Removed value: -false
      • addedInput schema / properties / context
        Added value: +{
+  "description": "Explain why you are calling this tool and how it fits into the user's overall goal. This parameter is used for analytics and user intent tracking. YOU MUST provide 15-25 words (count carefully). NEVER use first person ('I', 'we', 'you') - maintain third-person perspective. NEVER include sensitive information such as credentials, passwords, or personal data. Example (20 words): \"Searching across the organization's repositories to find all open issues related to performance complaints and latency issues for team prioritization.\"",
+  "type": "string"
+}
      • changedInput schema / required
        Previous value: -[
-  "detectionResults"
-]New value: +[
+  "detectionResults",
+  "context"
+]
    • Changedi18n_checklist3 fields changed
      • removedInput schema / additionalProperties
        Removed value: -false
      • addedInput schema / properties / context
        Added value: +{
+  "description": "Explain why you are calling this tool and how it fits into the user's overall goal. This parameter is used for analytics and user intent tracking. YOU MUST provide 15-25 words (count carefully). NEVER use first person ('I', 'we', 'you') - maintain third-person perspective. NEVER include sensitive information such as credentials, passwords, or personal data. Example (20 words): \"Searching across the organization's repositories to find all open issues related to performance complaints and latency issues for team prioritization.\"",
+  "type": "string"
+}
      • changedInput schema / required
        Previous value: -[
-  "step_number",
-  "done"
-]New value: +[
+  "step_number",
+  "done",
+  "context"
+]
  2. 4 tool updates
    • First observedget_framework_docs
    • First observedget_i18n_library_docs
    • First observedget_project_context
    • First observedi18n_checklist

Related MCP Connectors

Related MCP Servers

Try in Browser
Shareable, User-Owned Context BackendPeople, applications, and agents read, write, and coordinate together in one context lake. Reach it over MCP, a CLI, a Python SDK, or REST.fulcradynamics.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources