My First 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_current_timeB | 현재 날짜와 시간을 반환합니다. 시간대를 지정할 수 있습니다. |
| calculateC | 두 숫자의 사칙연산(덧셈, 뺄셈, 곱셈, 나눗셈)을 수행합니다. |
| get_random_numberC | 지정한 범위 내에서 랜덤 정수를 생성합니다. |
| reverse_stringB | 입력된 문자열을 뒤집어서 반환합니다. |
| get_server_infoB | 이 MCP 서버의 정보와 사용 가능한 Tool 목록을 반환합니다. |
| analyze_structureC | 프로젝트 디렉토리 구조를 분석하여 트리 형태로 보여줍니다. |
| analyze_dependenciesC | 프로젝트의 package.json을 분석하여 의존성 정보를 제공합니다. |
| count_linesC | 프로젝트의 코드 라인 수를 분석합니다 (코드/주석/빈줄 분류). |
| server_statusB | MCP 서버 상태를 확인합니다 (uptime, 메모리 사용량 등). |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| code-review | 코드 리뷰를 요청합니다 |
| explain-code | 코드 설명을 요청합니다 |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| server-info | MCP 서버 정보를 제공합니다 |
| config | 서버 설정 정보를 제공합니다 |
TDQS
Scored across 9 tools
Most tools have distinct purposes (e.g., analyze_dependencies vs. count_lines), but some overlap exists: get_server_info and server_status both relate to server monitoring, which could cause confusion. The descriptions help differentiate them, but the boundaries are not entirely clear.
The naming follows a consistent verb_noun pattern throughout (e.g., analyze_dependencies, calculate, get_current_time), with only minor deviations like 'server_status' using a noun_verb style. This consistency makes the tools readable and predictable.
With 9 tools, the count is reasonable, but the scope is broad and unfocused, mixing project analysis, basic utilities, and server monitoring. This makes it borderline as the tools don't form a cohesive set for a specific domain, feeling somewhat heavy for a general-purpose server.
The server lacks a clear domain, making completeness hard to assess. For project analysis, there are gaps (e.g., no update or delete operations for dependencies or structure). As a utility toolkit, it's incomplete with random tools like calculate and reverse_string that don't integrate well, leading to potential agent failures.