Skip to main content
Glama
mmntm

Weblate MCP Server

by mmntm

listProjects

Retrieve all translation projects available in Weblate for management and overview.

Instructions

List all available Weblate projects

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The handler function that implements the core logic of the 'listProjects' tool. It fetches projects using WeblateApiService, formats them into a markdown list, and returns them in the expected MCP content format. Handles errors gracefully.
    async listProjects() {
      try {
        const projects = await this.weblateApiService.listProjects();
    
        return {
          content: [
            {
              type: 'text',
              text: `Found ${projects.length} projects:\n\n${projects
                .map((p) => `- **${p.name}** (${p.slug})\n  URL: ${p.web_url}`)
                .join('\n\n')}`,
            },
          ],
        };
      } catch (error) {
        this.logger.error('Failed to list projects', error);
        return {
          content: [
            {
              type: 'text',
              text: `Error listing projects: ${error.message}`,
            },
          ],
          isError: true,
        };
      }
    }
  • The @Tool decorator registers the 'listProjects' function as an MCP tool, providing the name, description, and input schema (empty object since no parameters).
    @Tool({
      name: 'listProjects',
      description: 'List all available Weblate projects',
      parameters: z.object({}),
    })
  • Zod schema defining the input parameters for the tool (no parameters required).
    parameters: z.object({}),
Behavior2/5

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

With no annotations provided, the description carries full burden but only states the action without behavioral details. It doesn't disclose if this is a read-only operation, how results are returned (e.g., pagination, sorting), or any limitations (e.g., rate limits, authentication needs), leaving significant gaps.

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, efficient sentence that directly states the tool's purpose without any fluff or redundancy. It's front-loaded and wastes no words, making it highly concise and well-structured.

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 is incomplete for a list operation. It doesn't explain what 'list' entails (e.g., format, fields, ordering) or potential behavioral aspects, leaving the agent with insufficient context despite the simple parameterless design.

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 tool has 0 parameters with 100% schema description coverage, so no parameter documentation is needed. The description appropriately doesn't mention parameters, aligning with the schema, earning a high baseline score for not adding unnecessary information.

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 ('List') and resource ('all available Weblate projects'), making the purpose unambiguous. However, it doesn't differentiate from sibling tools like 'listComponents' or 'listLanguages' beyond the resource type, preventing a perfect score.

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 like 'getProjectStatistics' or 'getProjectDashboard'. It lacks context about use cases, prerequisites, or exclusions, offering only a basic statement of function.

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/mmntm/weblate-mcp'

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