Skip to main content
Glama

lawmadi-os

by io.github.peter120525-cmd
OverviewDiscussionsAdmin

find_village_lawyer

[KEY REQUIRED · no credits, 60/day] 법무부 '마을변호사'를 지역으로 찾습니다 — 무료 법률상담 연락처입니다. 시·도, 시·군·구, 읍·면 이름으로 검색하세요(예: '강원 강릉', '고성군', '완도'). 이 사업은 변호사가 없는 읍·면을 대상으로 하므로 서울·부산 등 특별시·광역시의 구(區)는 수록되어 있지 않습니다 — 결과가 0건이면 응답의 coverage 항목에서 수록된 시·도를 확인하세요. 공공데이터 기반, LLM 미호출. / Find the Ministry of Justice 마을변호사 (village lawyer) assigned to a Korean locality — a free legal-consultation contact point. The programme covers rural 읍·면 without a resident lawyer, so districts of Seoul and other metropolitan cities are not listed; an empty result returns the covered provinces. Public data, no LLM.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoMax results (1-50, default 10).
regionYesRegion name. Example: '강릉시'.
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.8/5.0
Behavior5/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 so: KEY REQUIRED, no credits, 60/day rate limit, public data source, no LLM call, and the empty-result/coverage behavior. These are non-obvious operational traits an agent needs before calling.

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?

Key operational facts (KEY REQUIRED, rate limit) are front-loaded and the critical coverage caveat is bolded. It is dense rather than bloated, though the full Korean/English duplication roughly doubles the length for the same information.

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?

No output schema exists, yet the description still tells the agent that an empty result returns covered provinces via a coverage field. Combined with the rate limit, key requirement, and coverage scope, an agent has everything needed to call correctly and interpret a null result.

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. The description adds value beyond the schema by showing multiple region-name formats ('강원 강릉' as a combined string, '고성군', '완도') and by explaining the coverage limitation that governs whether region matches anything, which the schema's single '강릉시' example does not convey.

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?

States a specific verb (find) plus resource (마을변호사/village lawyer) and the scope (assigned to a Korean locality, a free legal-consultation contact point). This is clearly distinguishable from siblings like lookup_precedent, lookup_statute, or search, which cover different legal resources.

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?

Explicitly says to search by 시·도, 시·군·구, 읍·면 name and gives concrete query examples ('강원 강릉', '고성군', '완도'). It also states the negative condition — metropolitan districts like Seoul/Busan are not covered — and tells the agent what to do on an empty result (check the coverage field). This is when-to-use, when-not, and fallback all in one.

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