Teams Guide 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 |
|---|---|
| get_guideC | 가이드 문서의 내용을 읽어서 반환합니다. |
| read_fileC | 외부 프로젝트의 파일을 읽어서 반환합니다. 절대 경로 또는 현재 작업 디렉토리 기준 상대 경로를 사용할 수 있습니다. |
| check_clean_codeC | 클린 코드 가이드를 기반으로 파일을 검사합니다. 가이드 문서를 참조하여 코드 품질을 분석합니다. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| clean-code-guide | 가이드 문서: clean-code-guide.md |
TDQS
Scored across 3 tools
The tools have distinct primary purposes: check_clean_code analyzes code quality, get_guide retrieves guide content, and read_file reads external project files. However, there is some potential overlap between get_guide and read_file, as both involve reading content, but their specific targets (guide vs. general files) help differentiate them.
The tools follow a consistent verb_noun pattern (check_clean_code, get_guide, read_file), with all using snake_case. The naming is clear and predictable, though 'check' and 'read' are slightly different verb styles, but this minor deviation does not hinder usability.
With only 3 tools, the server feels thin for a 'Teams Guide' purpose, as it might lack operations like updating guides or managing team-specific settings. However, the tools cover basic reading and analysis functions, making it borderline but not severely inadequate.
The tool surface is significantly incomplete for a 'Teams Guide' domain. It only supports reading and checking code against guides, with no tools for creating, updating, or deleting guides, managing teams, or handling user interactions, which are typical in such systems.