Skip to main content
Glama

Ireum — your name in Korean

Write a name in Hangul

write_name_in_hangul
Read-onlyIdempotent

Returns how a person's name (Latin letters, e.g. 'Emma', 'João') is written in Hangul, the Korean alphabet: the name itself spelled in Korean following Korea's official rules for foreign words (외래어 표기법), e.g. Emma → 엠마, Juliana → 줄리아나 (Brazilian Portuguese reading with language 'pt'). The result is a spelling of the name, not a Korean name. Also returns other common spellings and page links.

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

Input Schema

NameRequiredDescriptionDefault
nameYesThe first name in Latin letters, e.g. 'Emma'.
languageNoReading and link language: en (English names), es (Spanish), pt (Brazilian Portuguese). Default en.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), and the description adds behavior not in them: which transliteration standard is applied, that language choice changes the reading used, and that additional common spellings plus page links come back. It does not address failure behavior for unsupported names or characters, which keeps it at 4.

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

Conciseness4/5

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

The core statement is front-loaded and every sentence carries information — the standard, the examples, the disambiguation from a Korean name, and the extra return content. It is dense with nested parentheses and stacked clauses, making it slightly harder to scan than it needs to be.

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 compensates by disclosing the return content (Hangul spelling, other common spellings, page links), and both parameters are documented. Only edge-case behavior — unsupported scripts, unknown names — is left unstated for a tool whose whole job is lookup.

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 3 is the floor, but the description genuinely adds meaning: it explains that 'language' selects the source-language reading ('pt' = Brazilian Portuguese reading) and demonstrates the effect with Juliana → 줄리아나, which the enum description alone does not convey. It could still say what happens with a language/name mismatch, so not a 5.

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 and resource: it returns how a Latin-letter name is spelled in Hangul, with concrete examples (Emma → 엠마, Juliana → 줄리아나) and the governing rule set (외래어 표기법). The clause 'a spelling of the name, not a Korean name' directly separates it from find_korean_name without needing the schema.

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 clear context for when this tool applies — you have a Latin-script personal name and want its Korean spelling — and the 'not a Korean name' clause implicitly routes the agent away from find_korean_name for that case. It never names an alternative sibling explicitly or states any exclusion condition (e.g. non-Latin input, surnames), so it stops short of a 5.

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