Skip to main content
Glama
Sign In

NestDaddy

by com.nestdaddy
OverviewDiscussionsAdmin

news

Read-onlyIdempotent

Latest news headlines with links and summaries, refreshed every few minutes. topic: global, tech or financial. category: a section inside the topic (e.g. 'ai', 'crypto', 'stocks', 'politics'), or 'all'. 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). To find news about a subject, use news_search.

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

Input Schema

NameRequiredDescriptionDefault
limitNoHow many results to return, 1-50. Values outside the range are clamped.
topicNoWhich headlines: global (world), tech or financial (markets, crypto, economy).global
categoryNoA section inside the topic, e.g. ai, crypto, stocks, politics, or 'all'.all
full_textNotrue to also return the full article text of the first 5 results (each article read counts as one extra API call).

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • addedInput schema / properties / category / description
      Added value: +"A section inside the topic, e.g. ai, crypto, stocks, politics, or 'all'."
    • 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 / topic / description
      Added value: +"Which headlines: global (world), tech or financial (markets, crypto, economy)."
  2. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare read-only, idempotent, open-world and non-destructive behavior, and the description adds real value beyond them: the refresh cadence and the cost signal that each full-text read is an extra API call. Return shape is left to the output schema, which is acceptable 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?

Front-loaded with purpose, then a compact parameter rundown, then the sibling pointer. The inline 'topic: … category: …' listing is slightly redundant with the schema, but nothing is padded or misleading.

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?

Given rich annotations, an output schema, and fully described parameters, the description covers what an agent needs: what it returns at a high level, freshness, and the cost of full_text. Only cross-sibling disambiguation beyond news_search is missing.

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 coverage is 100% and the description's parameter notes (topic values, category examples, limit range, full_text cost) largely restate what the schema already documents. It adds marginal meaning, mainly the concrete category examples, so the baseline of 3 applies.

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 ('Latest news headlines with links and summaries'), plus freshness ('refreshed every few minutes'). It also explicitly contrasts itself with the sibling news_search, so an agent can pick between them without opening a 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 routing rule: use news_search to find news about a subject, implying this tool is for browsing current headlines. It does not address other plausible siblings such as country_news, so the when-not side is incomplete.

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

All NestDaddy toolsInspect
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.

Resources