Skip to main content
Glama

search_ai_law

Search Korean legal provisions using natural language queries. Find relevant articles without knowing the exact law name.

Instructions

[AI검색] 자연어로 관련 조문 의미검색. 법령명 몰라도 사용 가능. 법령명을 알면 search_law가 더 정확.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
queryYes자연어 질문 또는 일상 상황 (예: '음주운전 처벌', '임대차 보증금 반환', '퇴직금 계산')
searchYes검색범위: 0=법령조문(기본), 1=법령 별표·서식, 2=행정규칙 조문, 3=행정규칙 별표·서식0
displayYes페이지당 결과 개수 (기본값: 20)
pageYes페이지 번호 (기본값: 1)
lawTypesNo법령종류 필터 (예: ['법률', '대통령령', '총리령,부령']). 지정 시 해당 종류만 반환.
apiKeyNo법제처 Open API 인증키(OC). 사용자가 제공한 경우 전달
Behavior3/5

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

No annotations are provided, so the description carries full burden. It mentions 'AI 검색' and '의미검색' (semantic search) but does not disclose specific behaviors such as rate limits, authentication requirements, result format, or potential limitations beyond the comparison with search_law.

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?

The description is highly concise, consisting of two short sentences that immediately convey the tool's purpose and usage context. It is front-loaded with the most important information—purpose and key distinction from sibling tool.

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

Completeness3/5

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

While the schema covers parameters well, the description lacks information about output format, pagination behavior, or any response characteristics. For a tool with no output schema and no annotations, more contextual completeness would be beneficial. The description is adequate but not fully comprehensive for a tool with 6 parameters.

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

Parameters3/5

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

Schema coverage is 100%, and the input schema already describes each parameter adequately (e.g., query is '자연어 질문 또는 일상 상황'). The description adds no additional meaning beyond what is in the schema, so baseline score of 3 is appropriate.

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 clearly states it is an AI-powered semantic search for legal articles, using natural language. It explicitly distinguishes from the sibling tool 'search_law' by noting that if the user knows the law name, 'search_law' is more accurate.

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 when to use this tool ('법령명 몰라도 사용 가능') and when to use the alternative 'search_law' ('법령명을 알면 search_law가 더 정확'), providing clear guidance on tool selection.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/workbookbulb863/korean-law-alio-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server