Skip to main content
Glama

list_taxlaw_basic_ruling_laws

Retrieve a list of basic ruling laws from the Korean National Tax Service database to obtain law IDs for accessing detailed tax law texts. Filter by law name as needed.

Instructions

국세법령정보시스템 기본통칙 법령 목록 조회. get_taxlaw_basic_ruling_text의 lawId 확보용.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
queryNo법령명 필터. 예: 법인세, 소득세

Implementation Reference

  • src/index.ts:579-606 (registration)
    Tool registration in the tools array defining the name, description, and input schema for list_taxlaw_basic_ruling_laws
    {
      name: "list_taxlaw_basic_ruling_laws",
      description: "국세법령정보시스템 기본통칙 법령 목록 조회. get_taxlaw_basic_ruling_text의 lawId 확보용.",
      inputSchema: {
        type: "object",
        properties: {
          query: { type: "string", description: "법령명 필터. 예: 법인세, 소득세" },
        },
        required: [],
        additionalProperties: false,
      },
    },
    {
      name: "get_taxlaw_basic_ruling_text",
      description: "국세법령정보시스템 기본통칙 본문 조회. list_taxlaw_basic_ruling_laws 결과의 lawId 사용.",
      inputSchema: {
        type: "object",
        properties: {
          lawId: { type: "string", description: "기본통칙 법령 ID(ntstBscId)" },
          year: { type: "string", pattern: "^\\d{4}$", description: "연도. 미입력 시 최신 연도" },
          query: { type: "string", description: "통칙 제목/본문 내 필터" },
          display: { type: "number", minimum: 1, maximum: 200, default: 30 },
          full: { type: "boolean", default: false },
        },
        required: ["lawId"],
        additionalProperties: false,
      },
    },
  • Input argument interface for the list_taxlaw_basic_ruling_laws tool
    interface BasicRulingLawArgs {
      query?: string
    }
  • Handler function that calls ASISTD001MR01 action to fetch list of basic ruling laws and filters by optional query
    async function listTaxlawBasicRulingLaws(args: BasicRulingLawArgs): Promise<ToolResponse> {
      const data = await postTaxlawAction<BasicRulingData>("ASISTD001MR01", {}, "/st/USESTD001M.do")
      const query = cleanText(args.query).toLowerCase()
      const laws = (data.ASISTD001MR01?.bscExrDVOList || [])
        .filter((item) => !query || cleanText(item.ntstNm).toLowerCase().includes(query))
    
      if (laws.length === 0) {
        return notFoundResponse(`기본통칙 법령 목록에서 '${args.query || "(전체)"}' 결과가 없습니다.`)
      }
    
      const lines = [
        "국세법령정보시스템 기본통칙 법령 목록",
        `출처: ${TAXLAW_BASE}/st/USESTD001M.do`,
        "",
      ]
      laws.forEach((law) => lines.push(`[${law.ntstBscId || "N/A"}] ${cleanText(law.ntstNm) || "N/A"}`))
      lines.push("", "상세: get_taxlaw_basic_ruling_text의 lawId에 위 ID를 사용하세요.")
      return textResponse(lines.join("\n"))
    }
  • BasicRulingItem interface used by listTaxlawBasicRulingLaws to type the returned law items
    interface BasicRulingItem {
      ntstBscId?: string
      ntstNm?: string
      rgtYr?: string
      ntstExrBaseSn?: string
      ntstTextNm?: string
      ntstTextCntn?: string
      lawClCd?: string
    }
  • src/index.ts:1910-1911 (registration)
    Dispatch call in handleToolCall routing the tool name to the handler function
    if (name === "list_taxlaw_basic_ruling_laws") {
      return await listTaxlawBasicRulingLaws(input as BasicRulingLawArgs)
Behavior3/5

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

No annotations provided; description indicates a read-like query but lacks details on idempotency, rate limits, or response behavior. Adequate for a simple list operation, but could be more informative.

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?

Two sentences with no redundancy. Front-loads purpose then usage. Every word earns its place.

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

Completeness4/5

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

Given the tool's low complexity (single optional parameter, no output schema), the description is mostly complete. Lacks explicit mention of return format, but sufficient for an agent to infer usage.

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 parameter description in the schema already captures the filter purpose. The description adds no new semantic information beyond what the schema provides.

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?

Description clearly states the tool queries a list of basic ruling laws and specifies its role in obtaining lawId for get_taxlaw_basic_ruling_text. This differentiates it from sibling list tools.

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?

Explicitly identifies the primary use case (securing lawId for another tool), providing clear context. Does not include negative usage guidance, but specificity is high.

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/kim-go-chon/taxlaw-nts-mcp'

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