Skip to main content
Glama
ntv-mcp

ntv-mcp

ntv_search_news

Search recent n-tv headlines by keyword or phrase to find relevant news items, with result limits from 1 to 50.

Instructions

Keyword search over the LATEST n-tv headlines (the main feed holds roughly the last 50 — this is 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": "ntv_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.3/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 burden, and it does disclose the most consequential behavioral trait: the corpus is capped at roughly the last 50 items, so recall is bounded and results are freshness-weighted. It does not discuss auth needs, rate limits, or matching semantics (exact vs. fuzzy/phrase), which leaves some behavioral ground uncovered.

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?

Three short sentences, all front-loaded, with the scope caveat placed up front in parentheses where it matters most. The terse 'query:' / 'limit:' label style is slightly telegraphic but wastes nothing.

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 two-parameter search tool with an output schema already declaring return shape, the description covers purpose, scope, and both parameters adequately. Only the absence of matching semantics and of any pointer to sibling tools keeps it from being fully complete.

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, and it does: 'query' is defined as a keyword or phrase, and 'limit' is given a range of 1..50 that the schema does not encode (the schema only shows the default of 10). Matching behavior for multi-word queries is not spelled out, which is the remaining gap.

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 and resource ('keyword search over the LATEST n-tv headlines') plus an explicit scope boundary ('roughly the last 50 ... not a full-archive search'). That scope clause is what separates it from a browse-style sibling such as ntv_headlines or ntv_get_article, so an agent can route without opening either 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?

Gives a clear positive context (keyword/phrase lookup against current news) and an explicit exclusion (full-archive searching is out of scope). It stops short of naming an alternative tool for archive or browse use cases, so the agent must infer where else to go.

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