Skip to main content
Glama
Sign In
dw-mcp

dw-mcp

by mohammad-abbasi-sh
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

dw_topics

Find Deutsche Welle topic pages by keyword or list recently updated topics when no search term is given.

Instructions

DW topic pages matching a word (e.g. "bundesliga", "klima"). With no query, returns the most recently updated topics. language: e.g. "en", "de". 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_topics"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
queryNo
languageNoen

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior3/5

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

With no annotations, the description carries the full burden; it does disclose the no-query fallback behavior, which is genuinely useful. It says nothing about permissions, result ordering when a query is supplied, or pagination beyond the limit ceiling.

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?

Three short, front-loaded sentences with no filler; the default-behavior clause comes early. The compact fragment style for the parameter notes is terse but readable.

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 simple three-parameter read tool with an output schema, this covers purpose, default behavior, and every parameter's meaning. The main residual gap is result ordering when a query is provided.

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 coverage is 0%, so the description must compensate, and it does for all three parameters: example query terms, language codes ("en", "de"), and the limit range 1..50 with its default of 10. Only the language would benefit from a fuller enumeration.

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: it returns DW topic pages matching a word, with examples like "bundesliga" and "klima". It implicitly distinguishes itself from sibling article/headline tools by dealing in topics rather than articles, though it never names an alternative explicitly.

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?

It does offer one concrete usage rule: with no query it returns the most recently updated topics, which tells the agent this is also a browse tool. However, it gives no guidance on when to choose it over dw_search_news or dw_headlines for the same kind of lookup.

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