Skip to main content
Glama

Ireum — your name in Korean

K-pop Korean words

kpop_words
Read-onlyIdempotent

Korean vocabulary decks around popular K-pop (no lyrics): without 'deck' it lists the decks; with a deck id it returns its 10 words with romanization, meaning and a simple example sentence, and a link to study it.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "kpop_words"
  }
}

Input Schema

NameRequiredDescriptionDefault
deckNoDeck id. Leave out to list the decks.
languageNoLanguage of meanings and links: en, es or pt. Default en.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior4/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 useful behavioral context the annotations cannot: the content excludes lyrics, the result set is a fixed 10 words, and each entry carries romanization, meaning, an example sentence and a study link. It does not describe error behavior for an unknown deck, but the enum constrains that.

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 resource and then the two modes, with zero filler. Every clause (no lyrics, 10 words, romanization/meaning/example, study link) carries information an agent would otherwise have to discover by calling.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

There is no output schema, so the description carries the burden of describing return values, and it does so concretely (10 words, romanization, meaning, example sentence, study link). Combined with 100% schema coverage and full annotations, nothing an agent needs to call this correctly is missing.

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 both enums are documented, so the baseline is 3. The description still adds meaning beyond the schema by explaining the consequence of supplying 'deck' (returns that deck's 10 words with romanization, meaning, example sentence and study link) rather than merely restating the parameter.

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 resource (Korean vocabulary decks themed on K-pop) and states both operating modes: listing decks when no id is given, and returning a deck's 10 words with romanization, meaning, example sentence and study link. The '(no lyrics)' qualifier further pins down scope, so an agent can distinguish it from the name/hangul siblings without opening 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 explicit branching guidance: omit 'deck' to list decks, supply a deck id to get its words. That is clear when-to-use guidance for the tool's two modes. It does not mention when to prefer the sibling tools (find_korean_name, write_name_in_hangul), so it stops short of full alternative routing.

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