Skip to main content
Glama

KOREA WAVE NEWS

Search KOREA WAVE NEWS

search
Read-onlyIdempotent

Search articles, travel Q&A and guides on KOREA WAVE NEWS (Korean culture, K-pop, drama, beauty, food, Korean language, fashion). Returns id, title and URL.

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

Input Schema

NameRequiredDescriptionDefault
langNoLanguage code. Default ko. If the content is not available in that language, results fall back to the languages that exist.
limitNoNumber of results (default 5, max 10)
queryYesSearch words in any supported language

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered without description help. The description contributes only the return field list (id, title, URL) and nothing about ranking, result ordering, or behavior when a query matches multiple content types. That is useful but thin context beyond the structured data.

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 plus a return-value clause, with the resource and content scope front-loaded and the parenthetical topic list doing real work by signaling the corpus breadth. No filler, no restatement of the title, nothing to trim.

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 3-parameter read-only search with full schema coverage and complete annotations, the definition covers purpose, corpus, topic scope, and return fields, which is enough to call it correctly. The remaining gap is sibling differentiation and any note on result ordering or pagination, which matters less for a max-10-result tool.

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 description coverage is 100% and each parameter already documents its own semantics, including the language fallback behavior and the 1-10 limit bound. The description adds no syntax hints, query-language notes, or guidance on the lang parameter, so it neither compensates for nor improves on the schema. Baseline 3 applies.

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?

"Search articles, travel Q&A and guides on KOREA WAVE NEWS" gives a specific verb plus resource and enumerates the covered topic areas, so the agent knows exactly what corpus is queried. It falls short of a 5 because it never distinguishes itself from siblings like search_korea_guide, search_kpop_guide, or search_qa, which appear to overlap in scope.

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 enumeration of content types (articles, travel Q&A, guides) implies this is the broad catch-all search rather than a scoped one, which is usable inference. However, there is no explicit when-to-use or when-not-to-use statement and no sibling is named as an alternative, leaving the agent to guess how this differs from the three other search_* tools.

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