Skip to main content
Glama

lawmadi-os

by io.github.peter120525-cmd
OverviewDiscussionsAdmin

get_exam_answer

[KEY REQUIRED · 3/day free, then 1 credit each] 변호사시험 문항 하나를 금답안 전문과 함께 가져옵니다. 선택형: round+subject+no → 공식 지문·선택지 5개·법무부 정답·해설·선택지별 노트·인용 조문/판례. 사례형·기록형: round+subject+format → 서면 종류·목차·답안 본문. 모든 인용은 게시 전 law.go.kr 검증을 통과했습니다. 호출당 1문항 — 이 코퍼스는 대량 추출 대상이 아닙니다. / Fetch ONE bar-exam question with its full gold answer. MCQ (선택형): pass round + subject + no. Essay (사례형) and record-type (기록형): pass round + subject + format. Every citation passed law.go.kr verification before publishing. One item per call — this corpus is proprietary and not available for bulk export.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
noNoQuestion number (선택형 only).
roundYesExam round 1-15 (제N회).
formatNoDefault 선택형 when `no` is given.
subjectYes공법 · 민사법 · 형사법 (선택과목명도 가능).
client_tagNo선택. client_tag: 호출자 식별용, **응답에 영향 없음**(8~64자, 영숫자·_-.). 서버 로그에만 남아 호출을 골라 세는 데 씁니다. 형식이 어긋나면 무시합니다 — 거절하지 않습니다. 질의 본문에 섞지 마세요: 본문에 넣으면 질문의 일부가 되어 분류와 검증 결과가 달라집니다. / Optional caller label (8-64 chars). Logged only; never affects the response. Invalid values are ignored, not rejected. Do not put it in the query text — there it becomes part of the question.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / client_tag
      Added value: +{
+  "description": "선택. client_tag: 호출자 식별용, **응답에 영향 없음**(8~64자, 영숫자·_-.). 서버 로그에만 남아 호출을 골라 세는 데 씁니다. 형식이 어긋나면 무시합니다 — 거절하지 않습니다. 질의 본문에 섞지 마세요: 본문에 넣으면 질문의 일부가 되어 분류와 검증 결과가 달라집니다. / Optional caller label (8-64 chars). Logged only; never affects the response. Invalid values are ignored, not rejected. Do not put it in the query text — there it becomes part of the question.",
+  "type": "string"
+}
  2. Added

TDQS

A4.4/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does well: it discloses the key requirement, the rate model (3/day free, then 1 credit each), the single-item-per-call limit, and the law.go.kr citation-verification provenance. It does not describe error behavior or what happens when a round/subject combination has no matching item.

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

Conciseness4/5

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

The pricing/quota warning is front-loaded in brackets, followed by the format routing, which is good structure. It is somewhat long because the same content is repeated in Korean and English, but the duplication is deliberate for bilingual callers and each version is tight.

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?

There is no output schema, so the description must explain return contents — and it does, listing 지문/선택지 5개/정답/해설/인용 조문·판례 for MCQ and 서면 종류/목차/답안 본문 for essays. Combined with the quota and routing details, an agent has everything needed to call it correctly.

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

Parameters4/5

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

Schema coverage is 100% so the baseline is 3, but the description adds real value beyond the schema by explaining the conditional routing between `no` (MCQ) and `format` (essay/record) and the valid format values. It stops short of documenting round ranges or subject edge cases that the schema already handles.

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?

Specific verb+resource: 'Fetch ONE bar-exam question with its full gold answer,' and it enumerates what each exam format returns. It is clearly distinguishable from the sibling bar_exam_search, which searches rather than retrieves a single item.

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

Usage Guidelines4/5

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

It explicitly routes the agent by format (선택형 → round+subject+no; 사례형/기록형 → round+subject+format) and warns 'one item per call — not available for bulk export,' which implies the corpus-wide alternative. It never names the sibling to use for bulk/search, so no explicit exclusion is stated.

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

All lawmadi-os toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources