Skip to main content
Glama

Number to Korean amount words

kr_amount_to_korean
Read-onlyIdempotent

Write a won amount in Korean words exactly: reading form ("백이십삼만 사천오백육십칠 원", spaced every 만 per Korean orthography), contract/receipt form ("일금 일백이십삼만사천오백육십칠원정"), and mixed form ("123만 4,567원"). Whole numbers below 10^20.

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_to_korean"
  }
}

Input Schema

NameRequiredDescriptionDefault
amountYesWhole number; commas allowed, e.g. "1,234,567"

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and openWorldHint=false, so the safety profile is covered. The description adds genuine behavioral value by disclosing the three distinct output formats an agent will receive and the 10^20 upper bound, which is essential since no output schema exists.

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 sentence that front-loads the action and then spends every remaining word on concrete output examples. No filler, no restatement of the title, and the three forms are presented in a scannable parenthetical.

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?

With no output schema, the description carries the return-value burden and does so by showing all three formats verbatim, plus the numeric range. Minor gaps remain: nothing is said about behavior for zero, negatives, or out-of-range/non-integer input.

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 single amount parameter is already documented including comma tolerance; baseline would be 3. The description adds a constraint not in the schema — 'Whole numbers below 10^20' — which meaningfully bounds valid input.

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 verb and resource ('Write a won amount in Korean words') and enumerates the exact output shapes it produces, so the tool's function is unambiguous. It does not explicitly distinguish itself from the reverse-direction sibling kr_korean_to_amount, though the direction is clear from the description itself.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is implied rather than stated: an agent can infer this is the tool for converting numeric won amounts into Korean prose. There is no explicit when-to-use/when-not guidance and no mention of the inverse tool, leaving the agent to infer that kr_korean_to_amount is not a substitute.

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.