NestDaddy

news_search

Read-onlyIdempotent

Find news articles about anything by key words: every article NestDaddy collected from 45+ countries in the last 120 days, best match and newest first. The best tool for questions about recent events, people, companies and places. Use the words a headline would use, in the local language for local news (e.g. "banjir Jakarta" for Indonesian news). country: optional two-letter code (US, GB, SG ...). days: 1-120 (default 30). limit: 1-50 (default 10). full_text: true to also get the full text of the first 5 articles (each article read counts as one extra API call).

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": "news_search"
  }
}

Input Schema

Name	Required	Description
`days`	No	How many days back to search, 1-120.
`limit`	No	How many results to return, 1-50. Values outside the range are clamped.
`query`	Yes	Key words a headline would use, in the local language for local news.
`country`	No	Optional two-letter country code, e.g. US, GB, SG. Empty searches every country.
`full_text`	No	true to also return the full article text of the first 5 results (each article read counts as one extra API call).

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed5 schema fields changedNov 12, 2026

addedInput schema / properties / country / description

Added value: +"Optional two-letter country code, e.g. US, GB, SG. Empty searches every country."

addedInput schema / properties / days / description

Added value: +"How many days back to search, 1-120."

addedInput schema / properties / full_text / description

Added value: +"true to also return the full article text of the first 5 results (each article read counts as one extra API call)."

addedInput schema / properties / limit / description

Added value: +"How many results to return, 1-50. Values outside the range are clamped."

addedInput schema / properties / query / description

Added value: +"Key words a headline would use, in the local language for local news."

First observedNov 11, 2026

TDQS

A4.1/5.0

Behavior4/5

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

Annotations already declare readOnly, idempotent, openWorld and non-destructive, so the safety profile is covered. The description still adds real value beyond them: corpus coverage (45+ countries / 120 days), result ordering, and a cost disclosure that full_text reads count as extra API calls. It does not mention pagination or rate limits, but the billing caveat is the most important behavioral trait here.

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?

Purpose and scope come first, then a compact clause per parameter; nothing is padded with marketing filler. There is mild duplication of schema-stated defaults (days 30, limit 10) that could have been dropped, but the density is acceptable.

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?

An output schema exists so return shape needn't be explained, and the description covers corpus, ordering, query style and the extra-cost flag. What remains thin is guidance on choosing this over the sibling news tools, but for a single-query search tool the definition is otherwise sufficient to invoke correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so the schema already documents every parameter including ranges, defaults and the per-article cost of full_text. The description largely restates those defaults and the country code format, adding little beyond what is structured, which is the expected baseline for full coverage.

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 concrete verb and resource ('Find news articles about anything by key words') and immediately bounds the corpus: 45+ countries, last 120 days, ranked best match then newest first. An agent knows exactly what this returns and how it is ordered 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?

Gives explicit use-case guidance ('best tool for questions about recent events, people, companies and places') and even query-phrasing advice including local-language examples. It does not name when to prefer a sibling such as web_search or country_news, so routing among alternatives 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.

All NestDaddy tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.