Skip to main content
Glama
korean-tax-calc-mcp

korean-tax-calc-mcp

precheck_schema

Read-onlyIdempotent

Returns the required input keys, units, and mandatory fields for a Korean tax return precheck (법인, 부가, 소득). Use it to confirm parameters before running precheck or PDF tools.

Instructions

Tax return precheck input schema: keys, units and required fields (사전검토 입력스키마). 신고서 사전검토 입력스키마. 언제: return_precheck·영어로 된 신고서 PDF 도구 입력 전에 어떤 키를 넣어야 하는지 확인할 때. 입력: tax=법인|부가|소득. 결과: 각 입력키의 의미·단위·필수 여부를 목록으로 반환한다.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "tax": "<tax>"
    },
    "name": "precheck_schema"
  }
}

Input Schema

NameRequiredDescriptionDefault
taxYes사전검토 세목('법인'|'부가'|'소득')

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.9.1

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and closed-world, so the safety profile is fully covered. The description adds that the result is a listing of key meanings, units and required flags, which is useful but minimal. It says nothing about size of the response or how the enumeration relates to the calling tools' expectations.

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

Conciseness3/5

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

The when/input/result structure is front-loaded and easy to scan. However, the first clause duplicates the title in both English and Korean ('Tax return precheck input schema … 사전검토 입력스키마. 신고서 사전검토 입력스키마'), which is redundant rather than informative.

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?

For a one-parameter, read-only introspection tool with no output schema, the definition covers what it is, when to call it, what goes in, and what comes back. Little is missing, though a hint about the returned list's shape or how to feed it into the precheck tools would make it airtight.

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 covereage is 100% and the single parameter is an enum already documented in the schema with the same three values. The description's 'tax=법인|부가|소득' merely repeats the enum, adding no interpretation such as which tax type maps to which precheck tool.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific meta-resource: the input schema for tax-return precheck, listing keys, units and required fields, and explicitly says what it returns ('각 입력키의 의미·단위·필수 여부를 목록으로 반환한다'). This clearly differentiates it from the computation siblings like return_precheck, though the opening English phrase restates the title rather than adding scope.

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?

The '언제' clause gives a concrete trigger point: before supplying input to return_precheck or the English-PDF return tool, to confirm which keys are needed. That is clear, actionable context naming actual alternatives. It stops short of saying when this tool is unnecessary (e.g. if you already know the schema), so it is not a full 5.

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

Deploy Server

Other Tools