ntv-mcp

ntv_headlines

Fetches current n-tv headlines by section, letting you choose a category and limit results from 1 to 50.

Instructions

Latest n-tv headlines. section: "all" or one of politik, wirtschaft, sport, technik, panorama, wissen, der_tag. 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": "ntv_headlines"
  }
}

Input Schema

Name	Required	Description	Default
`limit`	No
`section`	No		all

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Nov 13, 2026

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 behavioral burden. It discloses the valid section values and the limit bounds with a default, which is genuinely useful validation context, but says nothing about ordering, recency window, or whether results are ever empty; the return shape is covered by the existing output schema.

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 compact sentences with the resource statement front-loaded and the two parameters documented immediately after. The colon-and-quote formatting is slightly telegraphic, but no sentence is wasted.

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?

This is a low-complexity, zero-required-parameter read tool with an output schema, and both parameters are documented in the description. The remaining gap is that 'latest' is never quantified (count-based or time-based), which mildly affects how an agent should combine it with the limit parameter.

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 schema declares no enum for section, so the description is the only source of valid values, and it lists all eight section options plus 'all'. It also documents the limit range (1..50) and its default of 10, adding real meaning beyond the bare integer schema.

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 names a specific resource (n-tv headlines) and scopes it with 'Latest', so the agent knows it retrieves a current headline feed. It does not distinguish itself from siblings such as ntv_search_news or ntv_get_article, which is what keeps it from a 5.

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?

Usage is only implied: the tool reads as a browse-the-latest-feed entry point, and the section enumeration hints at browsing by category. There is no explicit statement of when to prefer this over ntv_search_news or ntv_get_article, and no stated prerequisites.

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

Deploy Server