Skip to main content
Glama

Korean amount words to number

kr_korean_to_amount
Read-onlyIdempotent

Read a Korean money expression as an exact number: "1억 2천만 원", "삼백오십만원", "일금 일백만원정", "2.5억", "12만3천". Returns digits and comma form.

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": {
      "text": "<text>"
    },
    "name": "kr_korean_to_amount"
  }
}

Input Schema

NameRequiredDescriptionDefault
textYesKorean amount text

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive, and closed-world, so the safety profile is covered. The description adds the return shape ('digits and comma form'), which matters since there is no output schema, but it says nothing about error behavior on non-amount or mixed input, and does not clarify whether units such as 원 are included in the output.

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?

One sentence, verb-first, with the accepted-format evidence front-loaded before the return note. No filler, no restatement of the title.

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 single-parameter conversion tool with no output schema, the definition covers what goes in and roughly what comes out. Remaining gaps are edge-case behavior (invalid input, mixed digit/hangul strings, exact output formatting) which are minor but not zero for an agent handling messy real-world text.

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% and the single parameter is described only as 'Korean amount text', which is vague. The description's examples do real work here: they show that hangul numerals, 억/만 units, decimals, and formal 일금...정 forms are all valid inputs, adding meaning the schema does not convey.

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?

States a specific verb and resource ('Read a Korean money expression as an exact number') and anchors it with five concrete input examples spanning hangul numerals, 억/만 units, formal '일금...정' phrasing, and decimals. An agent knows exactly what transformation is performed. It does not name the inverse sibling kr_amount_to_korean, so sibling differentiation is only implied by the direction of conversion.

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?

The examples implicitly define when the tool applies (any Korean money string, with or without 원), but there is no explicit statement of when to prefer this over kr_amount_to_korean or what input classes are rejected. Usage is inferable from the sample strings rather than stated.

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.