Skip to main content
Glama
GalvinGao

SimpleLocalize MCP Server

by GalvinGao

get_environment_status

Check environment status in SimpleLocalize to view translation counts, languages, and resource availability for localization management.

Instructions

Get the current status of a specified environment.

This endpoint returns information about the environment including the number of keys, languages, non-empty translations, creation date, and available resources.

Args: environment_key: The environment key to check status for (e.g., "_latest", "_production", or custom key)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
environment_keyYes

Implementation Reference

  • main.py:174-205 (handler)
    The handler function decorated with @mcp.tool() that implements the logic to fetch and format the environment status from the SimpleLocalize API.
    @mcp.tool()
    async def get_environment_status(environment_key: str) -> str:
        """Get the current status of a specified environment.
        
        This endpoint returns information about the environment including the number of keys,
        languages, non-empty translations, creation date, and available resources.
        
        Args:
            environment_key: The environment key to check status for (e.g., "_latest", "_production", or custom key)
        """
        if not environment_key:
            raise ValueError("Environment key is required")
        
        try:
            result = await make_simplelocalize_request(
                "GET",
                f"/api/v2/environments/{environment_key}"
            )
            
            data = result.get("data", {})
            
            # Format the response in a readable way
            status_info = f"""Environment '{environment_key}' Status:
    - Number of keys: {data.get('numberOfKeys', 0)}
    - Number of languages: {data.get('numberOfLanguages', 0)}
    - Non-empty translations: {data.get('numberOfNonEmptyTranslations', 0)}
    - Created at: {data.get('createdAt', 'Unknown')}
    - Number of resources: {len(data.get('resources', []))}"""
            
            return status_info
        except SimpleLocalizeError as e:
            return str(e)
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It mentions what information is returned (keys, languages, translations, creation date, resources), which adds some context beyond basic purpose. However, it doesn't cover critical aspects like whether this is a read-only operation, potential rate limits, authentication needs, or error conditions—significant gaps for a tool with zero annotation coverage.

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 appropriately sized and front-loaded, with the core purpose stated first. The additional details and parameter explanation are relevant, though the structure could be slightly more streamlined (e.g., integrating the Args section more seamlessly). Overall, it's efficient with minimal waste.

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

Completeness3/5

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

Given the tool's moderate complexity (1 parameter, no output schema, no annotations), the description is partially complete. It covers the purpose and parameter semantics well but lacks usage guidelines and full behavioral transparency. For a status-checking tool, this is adequate but leaves gaps in guiding the agent effectively.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The description adds substantial meaning beyond the input schema, which has 0% description coverage. It explains that 'environment_key' is used to check status for, provides examples (e.g., '_latest', '_production', or custom key), and clarifies its role. This fully compensates for the schema's lack of documentation, making the parameter's purpose and usage clear.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the verb ('Get') and resource ('current status of a specified environment'), making the purpose evident. It distinguishes this as a status-checking tool among siblings that focus on translation operations (create, duplicate, get missing, etc.), though it doesn't explicitly contrast with them. The specificity is good but lacks explicit sibling differentiation.

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 guidance is provided on when to use this tool versus alternatives. While the description implies it's for checking environment status, it doesn't mention prerequisites, when it's appropriate (e.g., before publishing), or what other tools might be related. This leaves the agent without contextual usage cues.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/GalvinGao/mcp-simplelocalize'

If you have feedback or need assistance with the MCP directory API, please join our Discord server