LAWMADI
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| GEMINI_KEY | Yes | Gemini API key (used via Vertex AI) for LLM analysis. | |
| LAWGO_DRF_OC | Yes | law.go.kr API key (DRF API) for real-time statute verification. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| ask_ask_postB | Ask Main legal question endpoint — routes to 1 of 60 specialist agents with real-time statute verification. Responses:200: Successful Response (Success Response) Content-Type: application/json Output Schema: 422: Validation Error Content-Type: application/json Example Response: Output Schema: |
| ask_stream_ask_stream_postB | Ask Stream SSE streaming legal question — real-time token-by-token response with statute verification. Responses:200: Successful Response (Success Response) Content-Type: application/json Output Schema: 422: Validation Error Content-Type: application/json Example Response: Output Schema: |
| ask_expert_ask_expert_postB | Ask Expert Expert mode — full 4-Stage Legal Pipeline with deep analysis and comprehensive statute verification. Responses:200: Successful Response (Success Response) Content-Type: application/json Output Schema: 422: Validation Error Content-Type: application/json Example Response: Output Schema: |
| search_search_getC | Search Responses:200: Successful Response (Success Response) Content-Type: application/json Output Schema: 422: Validation Error Content-Type: application/json Example Response: Output Schema: |
| suggest_questions_suggest_questions_postB | Suggest Questions Suggest 3 contextual follow-up questions based on the current query and leader specialty. Responses:200: Successful Response (Success Response) Content-Type: application/json Output Schema: 422: Validation Error Content-Type: application/json Example Response: Output Schema: |
| get_leaders_api_leaders_getA | Get Leaders List all 60+ specialist legal agents (leaders) with their names, specialties, and profiles. Responses:200: Successful Response (Success Response) Content-Type: application/json Output Schema: |
| chat_leader_api_chat_leader_postC | Chat Leader 1:1 chat with a specific legal specialist leader via SSE streaming. Responses:200: Successful Response (Success Response) Content-Type: application/json Output Schema: 422: Validation Error Content-Type: application/json Example Response: Output Schema: |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| legal_question | Ask a Korean legal question — routed to the best specialist among 60 agents |
| expert_analysis | Deep 4-stage expert legal analysis with full statute verification |
| find_specialist | Find the right legal specialist for your situation |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| About Lawmadi OS | Overview of the Korean Legal AI service |
| Legal Domains | All 60 specialized legal domains covered by Lawmadi OS |
TDQS
Scored across 7 tools
The tools are mostly distinct in purpose (basic query, expert mode, streaming, chat with leader, list leaders, search, suggest questions), though some overlap exists between the various 'ask' tools. Descriptions help differentiate but an agent might still be confused about which to use.
Tool names are inconsistent and awkward, often duplicating segments (e.g., 'ask_ask_post', 'ask_expert_ask_expert_post') and mixing path components. This auto-generated style lacks a clear, user-friendly pattern.
With 7 tools, the server is well-scoped for a legal Q&A system. Each tool serves a distinct function without being too few or too many.
The tool set covers core interactions: asking questions (multiple modes), listing specialists, searching, and suggesting follow-ups. Minor gaps exist (e.g., no history or feedback), but the main workflow is supported.