Skip to main content
Glama

Ireum — your name in Korean

Find a Korean name

find_korean_name
Read-onlyIdempotent

Returns up to 3 real Korean given names for a person (their name in Latin letters, e.g. 'Emma', 'Sofía') — names people in Korea actually have that sound like it or share its meaning — plus how the name itself is written in Hangul (Emma → 엠마). Each name comes with Hangul, romanization, an easy 'sounds like' spelling, hanja and their meanings, why it matches, the first everyday Korean words built from the name, and a page link.

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": "find_korean_name"
  }
}

Input Schema

NameRequiredDescriptionDefault
eraNomodern = popular since 2000s, classic = 1980s–90s. Default any.
nameYesThe person's first name in Latin letters, e.g. 'Emma'.
genderNoGender feel of the Korean name. Default: the name's own.
languageNoLanguage of the meanings and links: en, es or pt. Default en.

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, openWorldHint=false and destructiveHint=false, so the safety profile needs no restating. The description does add real behavioral context beyond that: a hard cap of 3 results, the fact that names are filtered by sound or meaning, and a detail of the per-name payload (Hangul, romanization, hanja, meanings, page link).

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?

Front-loaded with the core capability and capped at one dense sentence with parentheticals. The lengthy enumeration of output fields is justified because no output schema exists, though the single mega-sentence structure makes it slightly harder to scan.

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 must describe return values, and it does so thoroughly — result count cap, per-name fields, and the link. For a simple read-only lookup with fully documented parameters, nothing an agent needs to call it correctly appears to be missing.

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?

Schema coverage is 100% with descriptive enums for era, gender and language, so the schema carries the parameter burden and baseline 3 applies. The description reinforces the 'name' parameter with a Latin-letter example but adds no new semantics for era, gender or language beyond what the schema already states.

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 ('Returns up to 3 real Korean given names for a person') plus the matching basis (sound-alike or shared meaning) and the output shape (Hangul, e.g. Emma → 엠마). This is clearly a Latin-name-to-Korean-name lookup, distinguishable from writing a name in Hangul or exploring K-pop vocabulary without opening any schema.

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 intended input (a person's first name in Latin letters) implies when to use it, but the description never states exclusions or points to alternatives such as write_name_in_hangul for pure transliteration. Guidance is inferable from the purpose rather than explicit.

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