byeori-mcp
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| BYEORI_URL | Yes | 벼리 주소. 예: http://127.0.0.1:8000 | |
| BYEORI_KB_ID | Yes | 볼 KB 의 번호(UUID). KB 관리 화면의 주소에 있다. | |
| BYEORI_API_KEY | Yes | 그 앱의 API 키. 벼리의 API 키 화면에서 발급한다. | |
| BYEORI_KB_DESCRIPTION | Yes | LLM 이 읽을 KB 설명. 무엇이 든 KB 인지 적는다. 예: "월별 수출입동향 보고서. 품목별 · 국가별 수출입 실적과 증감률." |
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": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_byeoriC | 월별 수출입동향 보고서. 품목별 · 국가별 수출입 실적과 증감률. |
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 1 tool
With only a single tool, there is no possibility of confusing it with another. Its purpose (monthly export/import trend search by item and country) is stated clearly enough that an agent knows exactly when to call it.
The sole tool uses a lowercase snake_case verb_noun form (search_byeori), which is readable and conventional. With only one name there is no pattern to validate against, and the mixed Korean/English domain term slightly reduces predictability.
One tool is thin for a data service, though its filters (by item, by country, monthly, growth rates) are folded into a single flexible search. It is borderline rather than clearly mismatched, since the domain is narrow.
The search covers the core lookup, but there are notable gaps: no way to list available periods, item codes, or countries, and no metadata or raw-data retrieval, forcing agents to guess valid filter values. Workable but with avoidable dead ends.