Skip to main content
Glama

Korea Number & Format Checks

Write a won amount in Korean

kr_amount_in_words
Read-onlyIdempotent

Write an amount in Korean won as words: formal (계약서·영수증 style, e.g. 금 일백이십삼만사천오백원정) and plain (e.g. 백이십삼만 사천오백 원).

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": {
      "amount": "<amount>"
    },
    "name": "kr_amount_in_words"
  }
}

Input Schema

NameRequiredDescriptionDefault
amountYes

Output Schema

NameRequiredDescriptionDefault
plainYes
formalYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior3/5

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

Annotations already cover safety (readOnlyHint, idempotentHint, closed-world), so the description's job is to disclose output behavior, and it does that by illustrating both the formal and plain orthographic conventions including the 금/원정 affixes. However, it never resolves whether both strings are returned in one call or whether some other mechanism selects one, which is the single most consequential behavioral fact for a caller. With an output schema present, some of that gap is mitigated, keeping this at a 3 rather than lower.

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?

A single front-loaded sentence states the operation, then the two output styles, each paired with a concrete example. No sentence is filler, and the parenthetical examples earn their length by resolving Korean-orthography ambiguity that prose could not.

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, single-purpose formatter with an output schema and full annotations, the description covers what the tool produces and in which styles, which is essentially everything needed. The only residual gap is the input range and boundary values, which the schema's minimum/maximum hint at but the description never confirms as intentional limits.

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?

There is one parameter with 0% schema description coverage, so the description must carry the load; 'an amount in Korean won' usefully fixes the unit as whole won and implies an integral value, matching the integer type. It says nothing about the accepted range (0 to 2^53-1) or edge behavior at zero or the maximum, so the semantic clarification is partial.

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 names a specific verb ('Write') and resource ('an amount in Korean won as words') and pins down the output precisely: two named styles with worked examples (금 일백이십삼만사천오백원정 and 백이십삼만 사천오백 원). This is unambiguous and does not overlap with the sibling tools kr_check_business_number or kr_normalize_phone, which handle entirely different data types.

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?

It gives real selection context by tagging formal style as 계약서·영수증 (contract/receipt) usage, so an agent can tell a downstream consumer which rendering applies where. It stops short of stating explicit exclusions or when-not-to-use, and it does not clarify whether the caller chooses a style or the tool emits both, but the practical guidance present is well above generic.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources