ntv-mcp

ntv_markets

Fetch recent n-tv Börse market news stories from the official RSS feed, with a limit of 1–50 items (default 10). Use it for headlines and market coverage, not live quotes.

Instructions

Latest n-tv market NEWS from the Börse feed (news stories about markets — not live quotes). 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_markets"
  }
}

Input Schema

Name	Required	Description	Default
`limit`	No

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Nov 13, 2026

TDQS

A3.7/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 usefully discloses the source feed (Börse) and that results are market news stories rather than live quotes, but says nothing about ordering/freshness semantics beyond 'Latest,' whether the feed can be empty, or any auth or rate constraints.

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 short clauses, front-loaded with the resource and scope, followed by the parameter constraint. No filler sentences and nothing 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?

For a single-parameter read tool with an output schema, the description covers source, freshness, the not-quotes caveat, and the limit range — enough to call it correctly. The only remaining gap is explicit differentiation from the other news siblings, which is left implicit.

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%, so the description must compensate for the single limit parameter, and it does: 'limit: 1..50 (default 10)' supplies the valid range and default that the schema does not. That is the key semantic the agent needs, though it does not say what happens on out-of-range values.

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 states a specific resource and qualifier: 'Latest n-tv market NEWS from the Börse feed,' plus the explicit disambiguation 'news stories about markets — not live quotes.' It narrows the domain enough that an agent can distinguish it from a quotes tool, though it does not explicitly distinguish it from siblings like ntv_headlines or ntv_search_news.

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 implied by 'Latest ... market NEWS' and the negative guidance 'not live quotes,' which tells the agent what this tool will not return. There is no explicit when-to-use versus ntv_headlines or ntv_search_news, and no stated prerequisites, so the routing guidance is inferred rather than stated.

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

Deploy Server