Skip to main content
Glama
Sign In
dw-mcp

dw-mcp

by mohammad-abbasi-sh
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

dw_headlines

Retrieves recent Deutsche Welle headlines in a selected language, with a configurable limit of 1–50 results for quick news monitoring.

Instructions

Latest DW headlines in one language. language: e.g. "en", "de", "fa-ir" (Iran Persian), "tr". limit: 1..50 (default 10).

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

Input Schema

NameRequiredDescriptionDefault
limitNo
languageNoen

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.3/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full behavioral burden, yet it only restates the two parameters. It says nothing about read-only nature, ordering of headlines, caching/freshness of "latest", or what happens with an unsupported language code.

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?

Two short sentences, front-loaded with the purpose, then immediately the parameter facts. No filler whatsoever; every clause carries information not present in the schema.

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 two-parameter read tool with an output schema, the essential calling information (both params, their ranges, defaults, and examples) is fully present. The remaining gap is positioning against sibling tools and any freshness/ordering semantics for "latest".

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 description coverage is 0% and the schema only supplies types and defaults, so the description does real work: it gives the limit range (1..50) with the default (10) and provides concrete language code examples including the unusual "fa-ir". It stops short of stating accepted code format or fallback behavior.

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?

States a specific verb and resource ("Latest DW headlines") plus a scoping constraint ("in one language"). Clear enough to know what it returns, but it never differentiates itself from the sibling dw_latest_articles, which sounds nearly identical.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

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

There is no when-to-use or when-not-to-use guidance, and no mention of any alternative. Given siblings named dw_latest_articles and dw_search_news, an agent must guess which to call, and the description offers nothing to resolve that.

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

Deploy Server

Other Tools