Skip to main content
Glama

KOREA WAVE NEWS

Latest news

get_latest_articles
Read-onlyIdempotent

List the newest KOREA WAVE NEWS articles, optionally by section.

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

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)
sectionNoSection name such as K-영화, K-POP (optional)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.3/5.0
Behavior2/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 by structured data. The description adds nothing beyond that — it does not characterize freshness (how "newest" is defined), the result cap, or the language fallback behavior that the schema mentions. For a well-annotated read tool this is thin but not contradictory.

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 no filler. The verb and resource come first, and the optional qualifier is placed at the end where it belongs.

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

Completeness3/5

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

With three optional parameters, full schema coverage, and rich annotations, the tool is simple enough that the description is largely sufficient. The main gap is that "newest" is never quantified (time window, ordering guarantee) and no sibling routing is offered, which matters given get_article, search, and other feed-like tools in the catalog.

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%: lang, limit, and section all have inline descriptions including the fallback rule, the default and max limit, and a section example. The description's only parameter-adjacent content, "optionally by section," restates the schema. Baseline 3 applies since the schema does the work and the description adds no new parameter meaning.

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 uses a concrete verb plus resource ("List the newest KOREA WAVE NEWS articles") and adds a scope qualifier ("optionally by section"). It reads clearly as a browse/latest-feed tool, distinct from a single-article lookup, but it never names a sibling to contrast against (e.g., get_article or search).

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?

"Optionally by section" implies the filtering use case and "newest" implies a discovery/browse use case, so some guidance is implicit. There is no explicit when-to-use vs. when-not, no mention of when to prefer search or get_article, and no statement of prerequisites.

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