Quokka Korea Tools

Korean age (만 나이)

kr_age

Read-onlyIdempotent

Compute international age (만 나이, the legal standard in Korea since June 2023) and year age (연 나이, used by the Youth Protection Act and military service) on a reference date. Input a birth date, or the first 7 digits of a resident registration number (YYMMDD-G) to also get sex and century. Feb 29 birthdays turn a year older on Mar 1 in common years. The input is not stored.

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": {
      "birth": "<birth>"
    },
    "name": "kr_age"
  }
}

Input Schema

Name	Required	Description	Default
`on`	No	YYYY-MM-DD. Omit for today in Korea (KST).
`birth`	Yes	1990-01-02, 19900102, 900102, or RRN front 900102-1

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 12, 2026

TDQS

A4.5/5.0

Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, and closed-world, so the safety bar is low; the description still adds real value with the privacy guarantee ('the input is not stored') and the Feb 29 / Mar 1 edge-case rule. It does not describe error behavior for malformed RRNs, which is the main remaining gap.

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?

Four compact sentences, front-loaded with the core computation, then inputs, then the leap-day edge case, then the privacy note. No filler or restatement of the title.

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?

With only two parameters, no output schema, and annotations covering the safety profile, the description supplies everything needed: what is computed, input formats, default reference date behavior, derived outputs, edge-case semantics, and data-retention policy.

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 exceeds it by explaining the consequence of the RRN input form — supplying the first 7 digits (YYMMDD-G) additionally yields sex and century, which the schema does not state. It also clarifies the birth parameter accepts either a birth date or an RRN fragment.

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 (compute) and specific resources (international age 만 나이 and year age 연 나이) with the legal context that distinguishes the two. No sibling tool covers age calculation, so there is no ambiguity to resolve, and an agent can tell immediately what it gets back.

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?

Explains when each output applies (만 나이 as the legal standard since June 2023; 연 나이 for the Youth Protection Act and military service) and that a reference date can be supplied. It does not state exclusions or point to alternatives, but no sibling offers comparable functionality, so the guidance is sufficient.

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

All Quokka Korea Tools tools Inspect

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

Need Help?