Skip to main content
Glama
Sign In
@langapi/mcp-server

@langapi/mcp-server

by TedyHub
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

get_translation_status

Compare source locale against target locales to identify missing and outdated translation keys, and estimate translation costs for your i18n project.

Instructions

Compare source locale against target locales to identify missing/outdated keys and estimate translation costs.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "source_lang": "<source_lang>"
    },
    "name": "get_translation_status"
  }
}

Input Schema

NameRequiredDescriptionDefault
source_langYesSource language code (e.g., 'en', 'pt-BR')
project_pathNoRoot path of the project. Defaults to current working directory.
target_langsNoTarget language codes. If not provided, all detected locales except source will be used.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.3

TDQS

B3.2/5.0
Behavior2/5

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

With no annotations provided, the description carries full burden for behavioral disclosure. It states the high-level function but does not disclose side effects (whether it is read-only), how missing/outdated keys are determined, what 'estimate translation costs' entails, or return format/error behavior.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single, front-loaded sentence that is concise and free of redundancy. Every word contributes meaning without repeating schema details.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the lack of annotations and output schema, the description should compensate by explaining what the tool returns and how to interpret results. It only describes the action, not the output structure or behavioral context, leaving significant gaps for an agent.

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?

The input schema already provides descriptions for all three parameters (100% coverage), so the description adds no additional parameter-level meaning. Baseline 3 applies as the schema does the heavy lifting.

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 uses a specific verb 'Compare' and clearly identifies the resource ('source locale against target locales') and outcomes ('identify missing/outdated keys and estimate translation costs'). It effectively distinguishes this tool from siblings like sync_translations and list_local_locales.

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?

No explicit guidance is given on when to use this tool vs alternatives. The description does not mention when not to use it or reference sibling tools, leaving the usage context only vaguely implied by the tool name and description.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools