Skip to main content
Glama

특정 시점 시행 조문

get_law_article_asof
Read-onlyIdempotent

특정 시점에 시행 중이던 조문 원문 조회 (law.go.kr 연혁 라이브).

get_law_article은 항상 현행이다. 과거 사건에 현행 조문을 적용하면 조용히 틀린
답이 된다 — 계약 체결·입찰공고·처분 시점이 과거이면 **반드시 이 도구를 쓰라**:
  - "2023년에 체결한 계약인데 지체상금률이 맞나"
  - "재작년 부정당업자 제재가 당시 기준으로 적법했나"
  - 감사·분쟁·소송 대응(적용법령은 행위시법이 원칙)

응답 필드:
  effective_date  그 시점에 시행 중이던 판의 시행일자
  is_current      그 판이 지금도 현행인가 (False면 이후 개정됨)
  prev/next_effective_date  직전·직후 개정 시행일 — 경계 판단용
  notes           미정비 상호인용 경고 (get_law_article과 동일)
  as_of_in_future 기준일이 미래여서 그 시점을 확정할 수 없음 (True면 아래 note를 읽어라)
  as_of_note      그 경우 무엇을 대신 돌려줬는지 — 미래 시점 적용법령을 단정하지 마라
  covered         우리 연혁 목록이 그 시점을 실제로 덮었는가 (False면 coverage_note를 읽어라)
  coverage_start/coverage_end  우리가 본 연혁의 시행일 범위
  versions_complete  연혁 목록을 끝까지 읽었는가 (False면 그 아래에 못 본 판이 있다)

**덮지 못하는 기준일에는 근사판을 주지 않는다.** 기준일이 그 법령의 최초 시행일보다
앞서면 `error: "asof_not_covered"` + `covered: false` + coverage_start/end가 온다 —
그때의 적용법령을 지어내지 말고, 우리 연혁이 어디서부터인지를 사용자에게 그대로 전하라.

**미래 날짜는 답할 수 없는 질문이다.** 아직 공포되지 않은 개정은 이 연혁에 없으므로
그 시점에 무엇이 시행 중일지 우리는 모른다. date가 미래면 오늘 기준 판을 주면서
`as_of_in_future=true`로 그 사실을 밝힌다 — 그 응답을 그 시점의 적용법령으로 쓰지 마라.

Args:
    ref: 조문 참조 (예: "국가계약법 제27조", "국가계약법 시행령 제26조")
    date: 기준일 "YYYY-MM-DD" 또는 "YYYYMMDD" (예: 계약 체결일)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
refYes
dateYes

TDQS

A5/5.0
Behavior5/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Beyond the read-only/idempotent annotations, the description discloses many non-obvious behaviors: uncovered early dates return asof_not_covered with coverage metadata rather than a approximate version, future dates return today's text with as_of_in_future true, and the agent must not invent applicable law for uncovered ranges. This is exactly the kind of behavioral context that prevents misuse.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Though long, the description is well-structured with bold headers, bullets, and front-loaded purpose. Every section earns its place: usage warning, response fields, error behavior, and argument examples, and since there is no output schema, the response-field list is necessary.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The description is exceptionally complete for a tool with no output schema: it covers purpose, sibling distinction, required argument semantics, response fields, coverage limits, error conditions, and future-date behavior. A agent has enough to call the tool correctly and interpret results without guessing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The input schema provides zero description for ref and date, so the description carries the full burden. It defines ref as an article reference with concrete examples and date as a 기준일 in YYYY-MM-DD or YYYYMMDD format with a contract-date example, and the prose further clarifies date edge cases like future dates.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description opens with a specific verb and resource: querying the original text of an article that was in force at a given time, backed by law.go.kr's history service. It also immediately distinguishes itself from get_law_article, which is always current, so an agent can tell the two apart without inspecting schemas.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description explicitly says get_law_article is always current and that applying it to past events silently gives wrong answers, and instructs to forcibly use this tool whenever the relevant event is in the past. It supplies concrete examples and even warns that future dates cannot be answered, telling the agent to not treat the returned text as applicable law.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.6/5.0
Disambiguation4/5

Each tool has a distinct role: decision-rules, price adjustment, delay penalties, exemption guidance, statute retrieval, case retrieval, and three specialized search tools. search_law, search_references, and search_cases look similar at first glance, but their descriptions clearly separate statutory text, full reference corpus, and caselaw/interpretation. The main ambiguity is between search_law and search_references for mixed practical queries.

Naming Consistency4/5

Almost all tools follow a snake_case verb_noun pattern: check_price_adjustment, decide_contract_method, estimate_delay_penalty, get_law_article, search_references. delay_exemption_guide is the one name that leads with a noun rather than a verb, and get_law_article_asof adds an as-of suffix that is not mirrored elsewhere, but the overall style remains predictable.

Tool Count5/5

Eleven tools are well-scoped for a Korean public-contract advisory server: three rule calculators, one exemption guide, paired search/retrieval tools, an as-of law lookup, and a feedback/question-log tool. Each tool earns its place, and the count is neither bloated nor too thin.

Completeness4/5

The server covers the main contract lifecycle well: selecting contract method, price escalation, delay penalty calculation, and delay exemption guidance, backed by statutes, references, and caselaw retrieval. Some narrower lifecycle aspects such as termination, sanctions, or post-award administration are only reachable through general search rather than dedicated decision tools, which is a minor gap agents can work around.