Skip to main content
Glama

kcsc-design-mcp

MCP server that brings the full text of national construction standards (KDS, KCS, etc.) straight into the AI chat window.

It connects to the Korea Construction Standards Center (KCSC) OpenAPI as-is. Enter your own API key and it works in any MCP-capable tool: Claude Desktop, Claude Code, Cursor, and others.

"KDS 14 31 10 의 압축부재 폭두께비 표 보여줘"
→ 표 4.2-2 를 마크다운 표 그대로 인용

⚠️ What this tool does not do

It does not do structural calculations for you.

  • Equations and symbols (λr, Fcr, etc.) do not come as text because the KCSC originals are images. This tool marks those spots as 〔그림 N〕 and never invents equations.

  • If you need the equation, use kcsc_formula to fetch the image as-is. That is the real equation from the real standard. If you calculate without looking at the image, the equation is not from the source — it is from the AI's memory — and it may be right or wrong, but you cannot tell which just by looking at the output. → In that case, verify the citations with kcsc_audit and disclose that fact.

  • The Excel files it creates are blank templates. It does not insert calculation formulas — the originals are images, so the formulas cannot be known, and putting an unknown formula into it is the start of an accident.

  • The bundled decision trees are not verified design documents. They are only review sequences and supporting clause references, and wherever KDS does not fix a value, a value adopted by the organization that made the tree is planted. You must replace it with your own organization's criteria; the responsibility for that decision lies with the engineer who uses it.

  • The final decision belongs to the engineer. A single wrong bridge load is a matter of a human life.


Related MCP server: KJH Law MCP

Installation

You first need an access key — apply for the OpenAPI at the Korea Construction Standards Center, https://kcsc.re.kr.

Claude Desktop / Claude Code

Put the following block into claude_desktop_config.json (or .mcp.json).

{
  "mcpServers": {
    "kcsc": {
      "command": "uvx",
      "args": ["kcsc-design-mcp"],
      "env": { "KCSC_API_KEY": "발급받은_키" }
    }
  }
}

If you do not have uvx, install uv first. There is no individual installation step.

Configuration locations — Claude Desktop (Windows): %APPDATA%\Claude\claude_desktop_config.json, Claude Code: the project's .mcp.json. After adding it and restarting the app, the 14 tools will be registered.

Using it directly from source

pip install -e .
KCSC_API_KEY=발급받은_키 python -m kcsc_mcp

Tools

Original text

Tool

What it does

kcsc_search(query, code_type, limit)

Finds standards by name (about 3,570)

kcsc_outline(code, code_type, depth)

Table of contents — hierarchical clause numbers

kcsc_read(code, section, code_type, max_chars)

Section text (tables kept)

kcsc_formula(code, section, code_type, max_images)

★The section's equations as images, untouched

kcsc_grep(code, keyword, code_type, limit)

Find sections in the body that contain the word

kcsc_audit(text, code)

Machine-verifies citations in a calculation answer (see below)

kcsc_version(code, code_type)

Version/update date (check for updates)

Design aids — decision trees

Tool

What it does

design_flows()

List of available trees (member, cross-section, design method, validation status)

design_map()

★Tree link map — which way the links go and what is still missing

design_flow(member, shape, method)

Design flow together with the supporting clause text for each step

design_sheet(member, shape, method)

Creates a blank section-check Excel → file path

design_validate(tree_yaml | path)

Validates tree — confirms actual clause numbers exist via the API

design_template(member, shape, method)

YAML skeleton for a new member

design_stamp(path | all_confirmed)

Stamps the confirmation time on a settled tree (검증일·검증기준) — if a standard has been revised, the validator flags it as a "tree confirmed under the previous edition"

Codes are all accepted in the forms KDS 14 31 10, 14 31 10, 143110. kcsc_grep and kcsc_version accept multiple codes separated by commas — since grep fetches an entire document and scans it, it accepts up to 10 at a time.


kcsc_formula — equations as intact images

Equations in the raw KCSC documents are GIF images. There is no alt text and no MathML, so the equations do not exist as text. The API key does not matter here — the key only grants access.

Actually though, the images themselves are sharp. So this tool returns the figure as is.

kcsc_formula('KDS 14 31 10', '4.2.3')

→ 텍스트 1개 + 이미지 17개
  〔그림 2〕  Pn = Fcr·Ag                    (4.2-1)
  〔그림 6〕  Fcr = [0.658^(Fy/Fe)]·Fy       (4.2-2)
  〔그림 9〕  Fcr = 0.877·Fe                 (4.2-3)
  〔그림 11〕 Fe = π²E/(KL/r)²               (4.2-4)

The numbers correspond to the 〔그림 N〕 markers in the kcsc_read body. While reading the text, you can pull only the equations you need.

The cost is practically trivial — roughly 27–216 vision tokens per 열절. However, some sections contain as many as 70 images, so by default only the first 40 are sent (adjustable with max_images).

※ Reading an image is also recognition, so a subscript can be misread. But the designer can also see the same image to compare — an equation filled in from memory has no compare target at all.


kcsc_audit — machine verification of citations in computed answers

Rather than blocking calculations, it makes the answer traceable. Give it an entire calculation answer and it pulls out and checks each reference — standard, clause, equation number, and table number — one by one.

## 인용 검증 — 6건 중 6건 확인 · 0건 실패

| 종류 | 기준 | 인용 | 확인 |
| 조항 | KDS 143110 | 4.3.2.1.1.4 | ✅ 강축 휨을 받는 기타 H형강…  ⚠️수식이미지 |
| 식   | KDS 143110 | 4.3-11      | ✅ 4.3.2.1.1.4 절에 있음 |
| 표   | KDS 143105 | 표 3.4-1    | ✅ 3.4.1 절에 있음 |

★4.3.2.1.1.4 절의 식은 원문이 이미지입니다. 도구가 읽지 못했습니다.
  → 이 계산에 쓰인 식·계수는 원문에서 온 것이 아니라 모델이 채운 것입니다.

Why it is needed — it actually happened. An H-section bending-review answer for an unusual H-beam (H-shaped cross) cited KDS 14 31 10 4.3.2.1.1.4 and took? — hmm, let me restart the English of the story:

Why — this really happened. An irregular H-beam bending-capacity review answer cited KDS 14 31 10 4.3.2.1.1.4, giving φMn = 83.8 kN·m, and when rechecked, every piece was correct. But that clause's original source contained no equations as text at all. The equation and its coefficient used in the answer were not obtained by reading the standard; the AI recalled them from memory.

It happened to be correct this time. The problem is that you — by looking at the output — cannot tell whether it is right or not.

What it cannot verify (must be read together):

  • Whether the equation content is correct — it cannot be, because the source is an image

  • Whether the clause applies to this member, this condition — that is a design judgment

  • Whether the arithmetic is correct

The only thing it confirms is the fact that, "the given number actually exists in the text at that place." If you read any more than that into the tool, the tool becomes a new kind of false reassurance.


Decision tree — 35 trees come with it

Design sequences are not embedded in code; they live outside as one YAML page = one member.

저장소 flows/   결정트리 35개 — LRFD 18 · 한계상태 9 · 허용응력 8 (이음 118개, 끊긴 곳 0)
패키지 동봉     형식 견본 1개 — `검증: 예제` 로 박아 둠. 그대로 쓰라는 게 아님
사용자 폴더     ~/.kcsc-mcp/flows/*.yaml   ← 여기에 두면 도구가 읽는다

Download flows/ and put it into ~/.kcsc-mcp/flows/, or point to the directory with KCSC_FLOWS_DIR. When the (member·section·design method) are the same, the user folder location can be moved — the user folder directory。

★Do not use the received trees as received. For any details where KDS does not provide values, the implementing organization may "adopted" values — deflection limit L/600, excluding outdated frequency strips, joint efficiency 75%/90%, and more. For there are, see the table in the directory flows/README.md. Must substitute your own organization's best goals. Place of expression equals exchange=..

A tree is design basis in scope, not a verified design document. A machine cannot prove that a given sequence is consistent with current industrial usage. The designer necessarily steps through each stage and has to judge.

To create your own tree, get a skeleton via design_template, fill it in, and check it with design_validate.

Wait — GXP7 has a heading after. Now the tree-linking paragraph; in my above table I may have accidentally reordered. Let me restructure the whole "trees" translation carefully to match original order:

Original order:

## 결정트리 — 35개가 함께 있습니다

설계 흐름은 코드에 박혀 있지 않고 **YAML 한 장 = 부재 하나**로 인길 있습니다.

GXP6

다운로드 [flows/](url)  — `~/.kcsc-mcp/flows/` — KCSC_FLOWS_DIR ... (?)

> ★주의...

자시 트리를...

### ★트리는 서로 이어져 있습니다

GXP7

...

### `design_validate` 가 포착하는 것

### ★분야 기본값은 **교량** 입니다

...

GXP8

...

### ★설계법의 사설 and data

But the user order actually:

1. ## 결정트리 — 35기가
2. Flow paragraph
3. GXP6
4. Download/copy paragraph
5. ★notice
6. design_template paragraph
7. ### ★트리는 서로 이어져...
8. "구조계산서는 not completes..." paragraph
9. GXP7
10. bullets
11. `design_map()` paragraph
12. ### `design_validate` 가 잡는 것
13. bullet list
14. "트리는 사람이 쓰고..." paragraph
15. ### ★분아 기본 기본값은 **교량** 임
16. ...

Good.

Note "GXP6" is right after the "YAML ... 바깥에 있습니다." paragraph; "GXP7" right after the connecting paragraph "should hand off ...". Yes.

Let me now render the "determ" section as proper sequence:

---

## Decision trees — 35 are bundled with it

Design flows are not baked into the code; they live outside, as **one YAML page = one member**.

GXP6

Download [`flows/`](https://github.com/lhs1152-lgtm/kcsc-design-mcp/tree/main/flows), put it in `~/.kcsc-mcp/flows/`, or point `KCSC_FLOWS_DIR` to that folder. If the same (member, cross-section, design method) exists, **your user folder beats the bundled sample.**

> ★**Don't take the bundled trees as-is.** Where KDS does not decide something, that space is a **value chosen by the organization that built the tree** — e.g., L/600 deflection limit, vibration threshold band etc. — see the table of [`flows/README.md`](url). **Replace them with your own organization's rules.**
>
> A tree is a **design rationale material, not a verified design sheet.** No machine can confirm that the flow matches real design. The designer must expand it step by step and decide.

To make your own, load the skeleton with `design_template`, fill it, **run the `design_validate` check**.

### ★Trees are linked together

Structural 계산서 does not finish with one tree. You can't just stop at the end of its own scope — it must link into the **next tree or the next standard.**

GXP7

* If `다다다` omits the **method**, the **current tree's method is dey** — when the method differs, the tree the tree and it's the same in the links.
* If the tree it points to does not exist yet, it says "not exists" — it never breaks the silent. What is left there exactly "what more must we build to make a structural handover?"... etc.

`design_map()` provides that map — which tree connects where, and **the referenced missing trees**, to boot. The 118 relations that are included in the 35 bundled trees are all linked, so broken 0. If you add, the map will prioritize by "what more is needed for complete structure's calculation report."

### What the validator’s `design_validate` caches

* schema missing / duplicate stage ID
* reference to a step without a branch — it ends right there
* **"made-up / mistyped / repealed" clause numbers** — whether it has confirmation of the actual clause in the standard via API
* — design method, "supporting basis" discrepancy — see below
* latest revision after confirmation that end — `검증`: the compare the issue (edition at confirm) at the time with the latest edition. If it’s revised, ❌ (that confirmation might no longer be valid)

"Tree is written by humans, but the machine verifies that its references exist. Fake clause number surviving will be the greatest danger." etc.

Now note flow: After this, "### ★분야 기본값은 **교량**입니다".

Then bullet and lines.

OK.

Now final answer. Let me ensure I include "GXP9" in the output as its own paragraph after the "same member different methods" sentence and before `method` bullets.

Also from that section: the ground basis "도구 neither enough" The slash.

Now, write the tail:

"`code_type` — 9 types — KCSC catalog contains not only national standard (KDS · KCS) but institutional special specifications:

| KDS | design standard | 561 |
| KCS | standard specification | 769 |
| SMCS | Seoul special construction specs | 853 |
| LHCS | LH special spec | 544 |
...
Keep headers:

| `도`: "Type" | meaning | count |

Now the translation table:
| KDS | Design base / Design standards | 561 |
| KCS | Standard publication (specification) | 769 |
| SMCS | Seoul Metropolitan Government Special Specification | 853 |
| LHCS | LH Special Specification | 544 |
| EXCS | Korea Expressway Corporation Special Specification | 328 |
| KRCCS | Korea National Railway Special Specification | 546 |
| KWCS | K-water Special Specification | 189 |
| NHCS | Korea Rural Community Corporation Special Specification | 76 |
| KRACS | Korea Airports Corporation Special Specification | 26 |

The original table: "KS코드 num" e.g. "KRCCS | 한국철도공사 전문시방서 | 546" Wait the number in the source is 226? Let me verify from the prompt: `| KRCCS | 한국철도공사 전문시방서 | 226 |`? The table in source above says "| KRCCS | 한국철도공사 전문시방서 | 226 |". In the user message: The line is `| KRCCS | 한국철도공사 전문시방서 | 226 |`. Yes, 226 (not 546). And "KRCS" row. I'll verify numbers: source table in prompt:

| KDS | 설계기준 | 561 |
| KCS | 표준시방서 | 769 |
| SMCS | 서울시 전문시방서 | 853 |
| LHCS | 임대 전문시방서 | 544 |
| EXCS | 한국도로공사 전문시방서 | 328 |
| KRCCS | 한국철도공단 전문시방서 | 226 |
| KWCS | 한국수자원공사 전문시방서 | 189 |
| NHCS | 한국농어촌공사 전문시방서 | 76 |
| KRACS | 한국공항공사 전문시방서 | 26 |

Yes.

Environment table:

| 변수 | 기본값 | 설명 |
| Need no code.

Continue: "환경변수" section.

Alright, final answer formatting. I'll now assemble fully. Make sure quotes about imm non — careful.

For "GXP" placeholder lines, I keep them on their own lines.

At the end, "Copyright (c) 2026 (주)하이드로코리아" — maybe translated to English? As org name, the user said keep org names. In the source "하이디로코리아" is the org, but since it's a Latin name in Hangul, I'd translate "HydroKorea" — Yet the instruction says verbatim. I'll write "Copyright (c) 2026 Hydro Korea Co., Ltd." or keep "(주)하이드로코리아"? Hmm. I'd keep the original as it is a name: "Copyright (c) 2026 (주)하이드로코리아" — but that's not "translated" English. However, as a licensed name, *subject to* preserving. The source says names kept "as they appear" — the name appears in Hangul. In translation, treating it as a proper noun would preserve it. I'll keep "HydroKorea" not because it's transliteration, but the known Latin name equals "Hydrokorea". I'll output "Copyright (c) 2026 Hydro Korea Co., Ltd." actually "Co., Ltd." is too much. Let me choose a middle: "Copyright (c) 2026 Hydro Korea". But the source includes "(주)", "주식회사" meaning incorporated. I'd translate: "Copyright (c) 2026 Hydro Korea Co., Ltd." Hmm. Given license header, probably OK.

But wait — translator instruction says "Return only translated text". Also "Keep organization names verbatim." If I change "하이드로코리아" to "Hydro Korea", is that verbatim? No. The safer route: keep as `(주)하이드로코리아` as is in the text, but then "주" is not readable... Hmm.

The required "Pros only" and "Keep org names verbatim" pushes me to keep the original string. I'll output "Copyright (c) 2026 (주)하이드로 코리아". But that may be jarring in an English doc. Given the explicit instruction, I'll keep it verbatim as "(주)하이드로코리아". Hmm, but then I am keeping Korean in the translation. The spec for "Keep verbatim" in list includes organization names: yes, they instruct to preserve.

Let's do it: "Copyright (c) 2026 (주)하이드로코리아". OK.

Now tn the 문의 at the end: "...를 [GitHub Issues](https://.../issues)로 받습니다." Keep the URL — yes.

Also "활용" — none.

Now, we must mirror the hyperlink URLS exactly given:
- <https://kcsc.re.kr/> (in the message it's <https://kcsc.re.kr>). Keep.
- https://docs.astral.sh/uv/
- flows/ URL: https://github.com/lhs1152-lgtm/kcsc-design-mcp/tree/main/flows
- flows/README.md URL
- docs/KCSC_API.md URL
- CHANGELOG.md URL
- License URL, flows LICENSE URL, Notice URL, issues URL.

Now produce final answer in Markdown. Also ensure SLDC "KSM" usage.

Let me assemble now. We will not wrap in code fence. Must "return only translated text". Good# kcsc-design-mcp

**An MCP server that lets you pull the original text of the National Construction Standards (KDS·KCS·etc.) directly into the AI chat console.**

It attaches the Korea Construction Standards Center (KCSC) OpenAPI directly. Enter your API key and use the standard with any MCP space-using tool — Claude Desktop, Claude Code, Cursor, etc.

GXP1

---

## ⚠️ What this tool does NOT do

**It does not do structural calculations for you.**

- Equations/symbols (λr, Fcr, etc.) do not come as text because the KCSC originals are **images**. This tool marks those places with `〔그림 N〕` and **does not make up an equation.**
- If you need an equation, get the **figure as it is via `kcsc_formula`.** That is the real equation from the real standard.
  If you calculate without looking at the figure, the equation is not from the original text, but from **AI memory** — and some are right and some are wrong, but you can't tell by looking at the output alone.
  → In that case, validate the citation with `kcsc_audit` and state that fact.
- The Excel it produces is a **blank template**. It includes no calculation equations — the source is an image, so we cannot know the equations. Adding an equation we do not know is an accident.
- **Available decision trees are not verified design documents.** They are just a review order and basis clauses, and for positions where KDS does not give a value, a value that the organization assumed is embedded. You must replace it with your own organization's best technique, and the responsibility for that judgement rests with the using design engineer.
- **The final decision is the designer.—**  one bridge load wrong is a casualty tragedy.

---

## Setup

The design key is required first — apply for the OpenAPI form at the Korea Construction Standards Site <https://kcsc.re.kr>.

### Claude Desktop / Claude Code

Put the following block in `claude_desktop_config.json` (or `.mcp.json`).

GXP2

If boot is not available, install [uv](https://docs.astral.sh/uv/) first. There is no separate install step.

Config file locations — Claude Desktop*Windows*, `%APPDATA%\Claude\claude_desktop_config.json`; Claude Code: the project `.mcp.json`. After adding and restarting, the 14 month tools will be picked up.

### Directly from source

GXP3

---

## Tools

### Origin source

| Tool | What it does |
| ----- | --------- |
| `kc_search(query, code_type, limit)` | Finds the code name **by name** (about 3,570) |
| `kcsc_outline(code, code_type, depth)` | Outline — of numbers really |
| `kcsc_read(code, section, code_type, max_chars)` | Text of a clause (**table preserved**) |
| `kcsc_formula(code, section, code_type, max_images)` | ★The section's **equations as images, intact** |
| `kcsc_grep(code, keyword, code_type, limit)` | Find sections containing that word **in the body text** |
| `kcsc_audit(text, code)` | **Machine reads citation in calculation answer** (see note below) |
| `kcsc_version(code, code_type)` | Version / revision date (check if revised, existing) |

### Design assistant — decision tree

| Tool | What it does |
| ----- | --------- |
| `design_flows()` | List of available trees (member, cross-section, **design code**, verification state) |
| `design_map()` | Tree **link map** — where it goes and **what not yet exists** |
| `design_flow(member, shape, method)` | Design flow + **fetch the basis clause text of each step

Available Tools

13 tools
design_flowA

부재의 설계 흐름을 단계별로 낸다. 각 단계의 근거 조항 원문을 함께 조회해 붙인다.

member: 부재 (예: 압축부재) shape: 단면 (예: 원형강관) method: 설계법 (예: 한계상태설계법 · 허용응력설계법). ★같은 부재·같은 단면이라도 설계법이 다르면 근거 기준 자체가 다릅니다. 트리가 여럿이면 되묻고, 임의로 고르지 않습니다. with_source: 각 단계의 근거 조항 원문을 함께 낼지. 끄면 흐름만 낸다. excerpt_chars: 단계마다 붙일 원문 길이.

※ 이 도구는 흐름과 근거까지입니다. 값 입력·계산·최종판단은 설계자가 합니다.

Inputs: member (required), shape, domain, method, +2 more. Returns: result

design_flowsB

쓸 수 있는 설계 결정트리 목록. 부재·단면·설계법·검증상태를 함께 낸다.

트리는 두 곳에서 읽는다 — 패키지 동봉 예제와 사용자 폴더(~/.kcsc-mcp/flows/*.yaml). 같은 조건이면 사용자 폴더가 이긴다 (각 회사의 트리가 그 회사 기준이다).

Inputs: no named parameters. Returns: result

design_mapC

트리 이음 지도 — 어느 트리가 어디로 이어지고, 무엇이 아직 없는지 낸다.

구조계산서는 트리 하나로 끝나지 않는다. 휨부재가 "약축"으로 판정되면 약축 트리로, 인장부재가 블록전단 검토로 가면 연결 기준으로 이어져야 한다. 이 도구는 그 연결을 한눈에 보여 주고 끊긴 곳을 목록으로 낸다. 그 목록이 곧 "완성하려면 뭘 더 만들어야 하는가" 다.

Inputs: no named parameters. Returns: result

design_stampA

확정 트리에 확정 시점 기록(검증일·검증기준)을 박는다.

path: 트리 파일 경로. (또는) all_confirmed: True 면 사용자 폴더의 검증: 설계자확정 트리 전부에 박는다(기록 없는 것만). date: 확정한 날(YYYY-MM-DD). 비우면 오늘.

검증기준 은 트리가 인용하는 기준마다 지금 API 가 주는 판({코드: 버전})이다. 이후 design_validate 가 지금 판과 대조해 기준이 개정되면 "구판으로 확정된 트리" 라고 잡아낸다. 확정 자체가 자동으로 유효하지 않게 되는 것을 놓치지 않기 위한 기록이다.

★기록을 박는 것은 기계지만, 개정된 기준을 다시 확인하는 것은 설계자다.

Inputs: date, path, all_confirmed. Returns: result

design_templateA

새 부재용 결정트리 YAML 뼈대를 낸다. 빈 폴더에서 형식을 몰라 못 시작하는 것을 막는다.

member: 부재 (예: 휨부재) shape: 단면 (예: H형강) method: 설계법. 비우면 한계상태설계법(LRFD)으로 채운다 — ★쓰기 전에 반드시 확인하세요.

낸 뼈대를 채워 ~/.kcsc-mcp/flows/ 에 넣고 design_validate 로 검사하세요. 근거로 적은 조항이 실재하는지 그때 기계가 확인합니다.

Inputs: shape (required), member (required), method. Returns: result

design_validateA

결정트리를 검사한다. ★적어 둔 근거 조항이 실재하는지 API 로 확인한다.

tree_yaml: 검사할 YAML 본문. (또는) path: 검사할 YAML 파일 경로. 둘 다 비우면 사용자 폴더의 트리를 전부 검사한다. check_refs: 근거 조항 실재 확인 여부. 끄면 스키마만 본다(빠르다).

잡아내는 것: · 스키마 누락 · 단계 식별자 중복 · 분기가 없는 단계를 가리키는 것(트리가 끊긴다) · 지어낸/오타난/폐지된 조항번호 — 기준에 그 절·표가 실제로 있는지 확인 · 설계법과 근거 기준의 불일치 (LRFD 트리가 허용응력설계법 기준을 근거로 삼는 등)

트리는 사람이 쓰고, 근거가 실재하는지는 기계가 검사합니다. 지어낸 조항번호가 그대로 남는 것이 제일 위험하기 때문입니다.

Inputs: path, tree_yaml, check_refs. Returns: result

kcsc_auditA

계산·검토 답변의 인용을 기계로 검증한다. 기준·조항·식 번호·표 번호가 실재하는지 확인.

text: 검증할 답변 글 전체를 그대로 넣는다. 안에서 인용을 뽑아 하나씩 확인한다. code: 기준이 하나뿐인데 글에 안 적혀 있으면 여기에 지정한다.

★구조계산 답변을 냈으면 이 검증을 함께 돌리고 결과를 밝히세요. KCSC 원문은 수식이 이미지라 도구가 읽지 못합니다. 그래서 계산에 쓴 식·계수는 원문에서 온 것이 아니라 모델이 기억으로 채운 것입니다. 맞을 때도 있고 틀릴 때도 있는데, 출력만 봐서는 구분이 안 됩니다. 이 도구는 그 경계를 드러냅니다.

확인하는 것: 기준 실재·버전 · 조항 실재 · 식 번호 실재와 그 식이 몇 절에 있는지 · 표/그림 번호 실재 · 그 조항의 식이 이미지인지 확인하지 못하는 것: 식의 내용 · 그 조항이 이 부재에 맞는지 · 계산이 맞는지

Inputs: text (required), code. Returns: result

kcsc_formulaA

★그 절의 수식을 이미지 그대로 가져온다. 식을 기억으로 채우지 않아도 된다.

code: 기준 코드 (KDS 14 31 10 등) section: 조항번호. 반드시 좁혀서 지정한다 (예: 4.3.2.1.1.4). 한 절에 이미지가 수십 개다. code_type: 코드가 겹칠 때만 지정. max_images: 최대 이미지 수. 0이면 기본 40.

KCSC 원문의 수식·기호는 텍스트가 아니라 GIF 이미지입니다 (alt 도 MathML 도 없음). 이 도구는 그 이미지를 그대로 돌려줍니다 — 본문의 〔그림 N〕 과 번호가 같습니다.

※ 이미지를 읽는 것도 인식이라 첨자를 잘못 볼 수 있습니다. 다만 설계자가 같은 그림을 볼 수 있어 대조가 됩니다. 기억으로 채운 식은 대조할 대상조차 없습니다. 최종판단은 설계자가 합니다.

Inputs: code (required), section (required), code_type, max_images.

kcsc_grepA

기준 본문에서 그 말이 있는 절을 찾는다. kcsc_search 가 못 보는 곳을 본다.

code: 기준 코드. 쉼표로 여러 개를 줄 수 있다 (예: KDS 14 31 10, KDS 14 31 05). 문서를 통째로 받아 훑기 때문에 한 번에 최대 10건까지만 받는다. keyword: 찾을 말. 띄어쓰기로 나눈 낱말이 모두 들어간 절을 찾는다. code_type: 코드가 겹칠 때만 지정. limit: 최대 절 수.

표 안의 글자도 함께 찾는다 — 기준의 값은 대부분 표에 있기 때문이다. 수식은 원문이 이미지라 찾을 수 없다 (〔그림〕 자리). 기호로는 검색되지 않는다.

Inputs: code (required), keyword (required), limit, code_type. Returns: result

kcsc_outlineA

기준의 목차(조항번호 계층)를 낸다. 어느 절을 읽을지 고르는 데 쓴다.

code: KDS 14 31 10 · 14 31 10 · 143110 다 받는다. code_type: 6자리 코드는 종류가 다르면 겹칠 수 있다. 겹치면 여기에 KDS·KCS 등을 지정한다. depth: 몇 단계까지 볼지. 3이면 4.2.1 까지. 0이나 음수면 전부.

Inputs: code (required), depth, code_type. Returns: result

kcsc_readA

기준 원문을 절 단위로 읽는다. 표는 표 그대로 보존된다.

code: KDS 14 31 10 · 143110 등. section: 조항번호. 4.2 를 주면 4.2.x 하위까지 전부 포함한다. 빈 값이면 문서 전체 (대개 매우 길다 — 먼저 kcsc_outline 으로 절을 고르는 편이 낫다). code_type: 코드가 겹칠 때만 지정. max_chars: 출력 상한. 0이면 기본값(KCSC_MAX_CHARS, 기본 20000).

※ 수식·기호는 원문이 이미지라 〔그림〕 으로만 나온다. 이 도구는 식을 지어내지 않는다. 이 원문을 근거로 계산했다면 식은 원문이 아니라 기억에서 온 것이므로, 그 사실을 밝히고 kcsc_audit 으로 인용을 검증할 것.

Inputs: code (required), section, code_type, max_chars. Returns: result

kcsc_versionA

기준의 버전·개정일을 확인한다. 개정 여부를 확인할 때 쓴다.

code: 기준 코드. 쉼표로 여러 개를 줄 수 있다. code_type: 코드가 겹칠 때만 지정.

카탈로그를 새로 받아 확인하므로, 결정트리의 근거 조항을 다시 검증해야 하는지 판단하는 데 쓸 수 있다.

Inputs: code (required), code_type. Returns: result

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    A4/5.0

    Scored across 13 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose: search by name vs. full-text grep, outline vs. read vs. formula retrieval, audit vs. version check, and the design_* tools each handle a different aspect (list, map, flow, validate, stamp, template). No two tools could be confused even without reading descriptions in detail.

    Naming Consistency5/5

    All tools follow a consistent pattern: either kcsc_<action> (search, outline, read, formula, grep, audit, version) or design_<noun/action> (flows, map, flow, validate, stamp, template). The prefix group is uniform, and the second part is a clear, consistent descriptor.

    Tool Count5/5

    13 tools is well within the ideal 3–15 range. The count reflects the domain's needs: 7 tools for standards retrieval/verification and 6 for design flow management, each earning its place without redundancy.

    Completeness5/5

    The tool surface covers the full lifecycle of standards lookup (search, outline, read, formula, grep), verification (audit, version), and design flow management (list, map, detailed steps, validation, stamping, template generation). Any gaps, like edit/delete of flows, are handled externally since flows are YAML files, and the deliberate separation of formula retrieval from reading addresses the image limitation.

    Maintenance

    ActivityInactive
    ResponsivenessNo recent community issues

    Related MCP Connectors

    Related MCP Servers

    • A
      license
      Not graded
      quality
      D
      maintenance
      Enables AI assistants to search, retrieve, and analyze South Korean legal documents including statutes, precedents, constitutional decisions, and administrative rulings via the Ministry of Government Legislation Open API. Provides 89 specialized tools with features like legal abbreviation auto-recognition, annex extraction, and complex research chain workflows.
      MIT