Skip to main content
Glama

KOREA WAVE NEWS

K-pop artist profile

get_artist
Read-onlyIdempotent

Get a K-pop group or singer profile Q&A from KOREA WAVE NEWS (debut, agency, members, fandom name, well-known songs) by name in Korean or English, e.g. BTS, 방탄소년단, aespa, IU.

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

Input Schema

NameRequiredDescriptionDefault
langNoko or en (default ko)
nameYesArtist name

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 readOnly, idempotent, non-destructive, and openWorldHint=false, so the safety profile is fully covered. The description adds that results come from a fixed KOREA WAVE NEWS corpus and what content categories to expect, but says nothing about behavior when the name is not found or when multiple artists match.

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 front-loaded sentence with the verb first, the payload in parentheses, and bilingual examples that each earn their place by demonstrating the name format. No filler or repetition.

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 usefully enumerates the profile fields an agent will receive and identifies the source corpus, which is enough to call it correctly with two simple parameters. The only meaningful omission is the not-found / ambiguous-name behavior.

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 baseline is 3, but the description goes beyond 'Artist name' by stating that names are accepted in Korean or English and giving concrete examples (BTS, 방탄소년단, aespa, IU). That is real added meaning for the required parameter, though the lang parameter's behavior is left entirely to the schema.

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 gives a specific verb and resource ('Get a K-pop group or singer profile Q&A ... by name') plus the source (KOREA WAVE NEWS) and the fields returned (debut, agency, members, fandom name, well-known songs). 'By name' implies a direct lookup, which separates it in spirit from the search_* siblings, but no sibling is named explicitly, so it stops short of a 5.

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 only implied: an agent can infer this is the tool to call when it already knows an artist's name and wants a profile rather than articles. There is no explicit when-to-use vs search_kpop_guide, search_qa, or get_article guidance, and no stated fallback when the artist is unknown.

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