meritz-codegen
OfficialServer 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 | {
"listChanged": true
} |
| logging | {} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| extensions | {
"io.modelcontextprotocol/ui": {}
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_categoriesB | 분류와 API 개수를 반환합니다. |
| search_apiA | 자연어로 API 를 찾습니다. 예: search_api('삼성전자 현재가'), search_api('매수'), search_api('실시간 체결통보'). category 로 좁힐 수 있습니다 (account·domestic_market·overseas_market·trading·forex·reference·realtime·oauth2). 인증(접근토큰 발급·폐기)은 '토큰'·'인증'·'oauth'·'revoke' 로 찾습니다. |
| get_api_detailA | api_type 의 상세를 반환합니다 — 경로·파라미터·응답 필드·주의사항. |
| generate_codeA | api_type 을 호출하는 Python 코드를 만듭니다. REST 는 토큰 발급·요청·응답 판정까지, 실시간은 웹소켓 구독 코드를 만듭니다. 주문·환전은 confirm=True 전까지 전송하지 않는 안전장치가 들어갑니다. api_type='token' 이면 토큰 발급 코드만 만듭니다. |
| api_conventionsA | 인증 절차·호출 규약·응답 코드·알려진 문제를 반환합니다. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| meritz_code_prompt | 작업 설명만 넣으면 검색→상세→코드 생성 흐름을 안내합니다. |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 5 tools
Each tool has a distinct role: search_api discovers APIs via natural language, get_api_detail provides specific API details, api_conventions offers general conventions, generate_code produces code, and list_categories gives a categorical overview. No overlapping purposes.
Four tools follow the verb_noun pattern (search_api, get_api_detail, generate_code, list_categories), but api_conventions deviates by being a noun phrase. The snake_case style is consistent, and the deviation is minor.
With 5 tools, the server is well-scoped for its code generation purpose. Each tool contributes to the discovery-to-code pipeline without redundancy or bloat.
The tool surface covers the full workflow: finding APIs, inspecting details, understanding conventions, generating code, and exploring categories. No obvious gaps for the intended code generation functionality.