Evolution MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
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
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
| prompts | {} |
| resources | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| generate_requirement_specB | 要件定義書を生成します。プロジェクト名、目的、背景から詳細な要件定義書（機能要件、非機能要件、制約事項など）を自動生成します。 |
| generate_functional_specA | 機能仕様書を生成します。機能一覧から詳細な機能仕様書（ユースケース、画面仕様、データ仕様など）を自動生成します。 |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| create_app | 4次元とシンプルさを込めた新しいアプリケーションを作成 |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| 4次元の原則 | 実存性・歴史性・関係性・非合理性：人が使い続けたくなるアプリの本質 |
| シンプルさの原則 | 3-1-1ルール：機能を最小化し、本質的価値を最大化する |
| デザイン原則 | Figma的UIの実装：プロフェッショナルで美しいインターフェース（必須要件） |
TDQS
Scored across 2 tools
The two tools target clearly distinct artifacts: a requirements definition document versus a functional specification document. The naming and descriptions make the boundary obvious, so an agent should not confuse them.
Both tools follow the same generate_<target>_spec pattern using consistent snake_case. This creates a predictable and uniform naming convention across the entire server.
With only two tools, the server feels thin and borderline for a document-generation server. Each tool is purposeful, but the set lacks supporting utilities or additional artifact types to feel fully scoped.
The pair covers the requirements-to-functional-spec handoff, but the workflow stops there. There is no way to update, version, or generate adjacent artifacts such as detailed design or test specifications, leaving notable gaps in a broader specification lifecycle.