spec-flow-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
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_development_specD | 获取开发规范 |
| list_specsB | 列出所有可用的开发规范 |
| create_development_specA | 创建新的开发规范，不允许覆盖已存在的规范 |
| edit_development_specB | 编辑已存在的开发规范，只能修改现有规范的内容 |
| delete_development_specB | 删除已存在的开发规范 |
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 5 tools
Each tool targets a distinct action (get, list, create, edit, delete) on the same resource, with no overlap in functionality. An agent can easily distinguish them.
Most tools follow a verb_noun pattern with 'development_spec', but 'list_specs' abbreviates the noun slightly. This minor inconsistency does not significantly hinder understanding.
Five tools cover all basic CRUD operations for a single resource, which is well-scoped and appropriate for the server's purpose.
The set includes create, read (both single and list), update, and delete operations, covering the full lifecycle for development specs. No obvious gaps.