Skip to main content
Glama

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
Generation moduleC
 遍历工具返回的数组,将数组中每一项有 writeOptions: object、dir: string,两个属性。
 需要将对象writeOptions的属性进行遍历,找到dir文件中对应的变量名。 匹配规则:变量名和writeOptions的属性名称相等。
 匹配到了之后将dir中的变量值自动重写,使用writeOptions属性值覆盖,一定是自动重写。
 For example: 
 writeOptions示例
 ``` javascript
   writeOptions:{subnaem:'用户管理'}
 ```

 dir文件代码示例:
 ``` javascript
   const subnaem = '';
 ```

 经过规则匹配之后,dir文件重写后应该是:
 ``` javascript
   const subnaem = '用户管理';
 ```

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

C2.4/5.0

Scored across 1 tool

Disambiguation5/5

With only one tool named 'Generation module', there is no possibility of confusion or overlap with other tools. The tool's purpose is clearly defined as a specific file rewriting operation based on matching rules, making it entirely distinct by default.

Naming Consistency3/5

The tool name 'Generation module' uses a noun-based naming style, which is readable but lacks a consistent verb_noun pattern that is typical for action-oriented tools. Since there is only one tool, consistency cannot be assessed across multiple tools, but the naming is clear though not following common conventions.

Tool Count2/5

A single tool for a server named 'MCP Server Starter' feels thin and under-scoped, as it suggests a limited or incomplete surface. Typically, such a server might be expected to offer more foundational or varied tools for starting or managing MCP servers, making one tool insufficient for the implied purpose.

Completeness1/5

The tool set is severely incomplete for the server's purpose. With only one tool focused on a niche file rewriting task, there are significant gaps in coverage for common MCP server operations like configuration, deployment, or management, leading to likely agent failures in broader tasks.