Skip to main content
Glama

dw_search_news

Search recent Deutsche Welle headlines by keyword and language to find current news coverage; results are limited to recent sitemap entries, not the full archive.

Instructions

Keyword search over the LATEST DW headlines (the news sitemap holds roughly the last 50 — this is not a full-archive search). query: keyword or phrase. language: e.g. "en", "de", "fa-ir". limit: 1..50 (default 10).

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

Input Schema

NameRequiredDescriptionDefault
limitNo
queryYes
languageNoen

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.2/5.0
Behavior4/5

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

No annotations are present, so the description carries the full behavioral burden, and it delivers the single most important trait: the index is shallow (roughly the last 50 headlines), so results can silently omit older matching stories. Return values are covered by the existing output schema. It is silent on result ordering and whether matching is substring or headline-only, which keeps it below a 5.

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?

The scope caveat is front-loaded and every clause earns its place, with zero filler. The trailing parameter list is terse to the point of being fragmentary, which is efficient but slightly dense to parse.

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 three-parameter read-only search with a documented output schema, the definition covers purpose, index limits, and every parameter, which is nearly everything needed to call it correctly. What remains missing is modest: result ordering and any explicit fallback tool for older content.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description must compensate, and it does for all three parameters: query is a keyword or phrase, language is given format examples ("en", "de", "fa-ir"), and limit is bounded to 1..50 with a default of 10 — bounds and default that the raw schema does not express. This is meaningful added semantics beyond the structured fields.

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+resource ("keyword search over the LATEST DW headlines") and immediately bounds the scope with the note that the news sitemap holds roughly the last 50 items and is not a full-archive search. That scope statement effectively separates it from a full-archive search and, by implication, from headline/listing siblings. It stops short of naming a sibling such as dw_latest_articles or dw_headlines to contrast with, so it is clear but not fully differentiated.

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?

The definition supplies a clear usage condition (find recent news by keyword or phrase) plus an explicit when-not (no archive coverage beyond ~50 items), which is the exact boundary an agent needs to avoid a wrong selection. It does not point at an alternative tool for the archive case, so the guidance is clear but not complete routing.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.