Skip to main content
Glama

dlf_news_by_topic

Retrieve Deutschlandfunk news items filtered by a chosen topic such as politics, culture, or sport, with an optional result limit.

Instructions

Deutschlandfunk news by topic. topic: europa, gesellschaft, wirtschaft, wissen, kultur, sport or politik. 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": {
      "topic": "<topic>"
    },
    "name": "dlf_news_by_topic"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
topicYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.3/5.0
Behavior3/5

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

With no annotations at all, the description carries the full burden but only discloses the limit bounds (1..50, default 10). It says nothing about result ordering, freshness, language, rate limits, or error behavior for an invalid topic. The presence of an output schema lowers the bar for explaining return values, keeping this at a minimum-viable 3.

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?

Two short lines, front-loaded with the resource and immediately followed by the parameter facts; nothing is padded. The telegraphic phrasing is slightly less scannable than full sentences but costs no tokens.

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?

For a two-parameter read tool with an output schema, both parameters are now documented, so the essentials are covered. Missing are behavioral details that matter for an unannotated tool: whether results are newest-first, what an invalid topic returns, and how it relates to the other news siblings.

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% with no enums defined, so the description does real work by enumerating the seven valid topic strings (europa, gesellschaft, wirtschaft, wissen, kultur, sport, politik) that the schema leaves as a free string. It also adds the missing 1..50 bound on limit beyond the schema's default of 10, leaving only minor gaps such as case sensitivity.

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?

Names a specific resource (Deutschlandfunk news) with a filtering dimension (by topic), so the agent can tell it retrieves topic-scoped news. It does not differentiate itself from the overlapping siblings dlf_latest_news or dlf_search_news, which also return news.

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 named alternative; the agent must infer from the title alone that this is for a single-topic feed versus a keyword search or a general latest feed. The only guidance offered is the allowed topic values, which is parameter information rather than usage routing.

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