Skip to main content
Glama
oofengoo

MCP-Serve 多语言翻译服务

by oofengoo

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault

No arguments

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Capabilities

Server capabilities have not been inspected yet.

Tools

Functions exposed to the LLM to take actions

NameDescription
translationI18nD
copyI18nD

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

D1.2/5.0

Scored across 2 tools

Disambiguation1/5

The two tools have overlapping purposes with no descriptions to clarify differences. 'copyI18n' and 'translationI18n' both appear to handle i18n (internationalization) tasks, making them indistinguishable. An agent cannot determine when to use one versus the other, leading to high misselection risk.

Naming Consistency3/5

The naming shows mixed conventions: 'copyI18n' uses camelCase while 'translationI18n' uses a similar style but with a different prefix. Both include 'I18n', providing some thematic consistency, but the lack of a clear verb_noun pattern and the variation in prefixes ('copy' vs. 'translation') reduces predictability.

Tool Count2/5

With only 2 tools for a '多语言翻译服务' (multilingual translation service), the count feels too thin. A translation service typically requires more operations, such as translate_text, detect_language, or manage_translations. This minimal set limits functionality and suggests an incomplete implementation.

Completeness1/5

The tool surface is severely incomplete for a translation service. There are no tools for core operations like translating text, detecting languages, or managing translation keys. The two vague tools do not cover the domain's essential workflows, leaving significant gaps that will cause agent failures.

Maintenance

ActivityInactive
ResponsivenessNo issues