Skip to main content
Glama

dlf_search_news

Search recent Deutschlandfunk news items by keyword or phrase and return matching results, so you can find current coverage on a topic without browsing the feed.

Instructions

Keyword search over recent Deutschlandfunk items (the Agenda feed, several hundred latest items — not a full-archive search). query: keyword or phrase. 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": "dlf_search_news"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
queryYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.4/5.0
Behavior4/5

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

No annotations are supplied, so the description carries the full disclosure burden, and it delivers the most important trait: results are limited to a few hundred recent Agenda-feed items, so absence of a hit does not mean absence in the archive. It omits result ordering (relevance vs. recency) and any auth/rate-limit characteristics, leaving some behavioral gaps.

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?

Scope is front-loaded in the first clause, then each parameter gets a single compact gloss. No sentence is redundant and the size matches a two-parameter tool.

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?

With an output schema present, return format need not be explained, and the corpus-scope caveat covers the main correctness risk for a search tool. Ordering and pagination expectations are the remaining unaddressed items, though the small corpus and limit cap make pagination largely moot.

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: 'query' is described as a keyword or phrase, and 'limit' gains the 1..50 range that the schema itself does not encode (the schema only has a default of 10). Minor gap is search semantics for phrases (exact match vs. term AND).

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 (keyword search) and resource (Deutschlandfunk items) and immediately bounds the corpus: 'the Agenda feed, several hundred latest items — not a full-archive search.' An agent knows exactly what will and will not be searched 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 Guidelines4/5

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

The 'not a full-archive search' exclusion gives a clear when-not, and the recent-items scope implies when this beats browsing. It does not name a sibling (e.g. dlf_latest_news for unfiltered browsing or dlf_news_by_topic for topical exploration), so the alternative-selection step is left to inference.

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