Majin Slide MCP
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
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| generate_slide_promptA | Marp用のプレゼン資料プロンプトをトピックから生成します(既定で10枚想定)。ユーザーが“スライドを作って/説明して/要点をまとめて”など資料化やプロジェクト・機能説明を求めた場合に積極的に実行してください。返却テキストはモデルへの指示文としてそのまま利用できます。 |
| create_slide_fileA | 生成済みのMarkdownスライドを.mdファイルとして保存します。モデルがMarkdownを出力した直後に続けて実行してください(同名があれば上書き)。 |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 2 tools
The two tools have completely distinct and non-overlapping purposes: one generates a prompt for creating slides, while the other saves generated slides to a file. There is no ambiguity or confusion between them, as they serve different stages in the slide creation workflow.
Both tools follow a consistent verb_noun naming pattern (generate_slide_prompt and create_slide_file), using snake_case and clear action-object pairs. This consistency makes the tools easily understandable and predictable in their naming.
With only two tools, the server feels under-scoped for a slide creation domain, as it lacks essential operations like editing, deleting, or listing slides. While the tools cover prompt generation and file saving, the overall functionality is thin and incomplete for typical presentation workflows.
The server is severely incomplete for slide creation, missing core CRUD operations such as updating or deleting slides, and lacking tools for managing slide content or metadata. The two tools only address initial generation and saving, leaving significant gaps that will hinder agent effectiveness in handling full slide lifecycle tasks.