Skip to main content
Glama

KOREA WAVE NEWS

Get an article

get_article
Read-onlyIdempotent

Get one news article (title, date, section, summary and body) by article id such as KW20261115020 or by 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": {
      "id": "<id>"
    },
    "name": "get_article"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesArticle id (KW...) or URL

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/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 covered. The description adds value beyond that by listing exactly which fields come back, which matters given there is no output schema. It does not cover behavior on a missing/invalid id, a minor gap.

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?

A single front-loaded sentence with the resource, returned fields, and accepted identifier forms in that order — no filler. Slightly dense parenthetical list, but nothing is wasted.

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 one-parameter, idempotent read tool with full schema coverage and no output schema, the description supplies the needed return-field summary and accepted id forms. Only error/not-found behavior is unaddressed, which is a small omission at this complexity.

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% and the sole parameter already documents 'Article id (KW...) or URL'. The description reinforces this with a concrete example id (KW20261115020) and the dual id/URL acceptance, but adds little beyond the schema text, so the baseline of 3 applies.

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 ('Get one news article') and enumerates the returned fields (title, date, section, summary, body), which implicitly separates it from get_latest_articles (plural/latest) and search (query-based). An agent can tell this is a single-record lookup 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 Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The 'by article id ... or by URL' phrasing implies when to use it — you already have an identifier — but it never names an alternative such as search or get_latest_articles, nor states what to do when no id is known. Usage is inferable 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