Skip to main content
Glama

dlf_latest_contributions

Fetch recent Deutschlandfunk articles and audio features with an adjustable result limit of 1 to 50, enabling quick monitoring of current public-radio coverage without authentication.

Instructions

Latest Deutschlandfunk contributions (articles & audio features). 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": "dlf_latest_contributions"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/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 burden of behavioral disclosure. It implies a read-only retrieval but never says so explicitly, and says nothing about ordering, freshness window, pagination, or whether audio features carry extra fields; the only concrete behavior given is the limit bound.

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 terse elements: the purpose first, then the parameter constraint. No filler, nothing buried, and the constraint sits right where an agent scanning for limits would look.

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?

An output schema exists, so return values need not be described, and the single parameter is bounded. What is missing is sibling disambiguation against a catalog that contains a very similarly named news-latest tool, leaving the selection decision under-supported.

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% and the single parameter has no description, so the description must compensate. It does meaningfully, supplying both the valid range (1..50) and the default (10), which the schema itself does not encode and which prevents invalid calls; it does not explain what is being counted, hence not a 5.

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 resource ('Deutschlandfunk contributions') and clarifies the content types ('articles & audio features'), so the agent knows it retrieves a recent-items feed. It stops short of distinguishing itself from the close sibling dlf_latest_news, which an agent must disambiguate on its own.

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 guidance on when to pick this over dlf_latest_news, dlf_search_news, or dlf_news_by_topic, and no stated preconditions. The agent is left to infer that this is the broad 'everything recent' feed.

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