Skip to main content
Glama

Noozra

by com.noozra
OverviewDiscussionsAdmin

Latest news

latest_news
Read-onlyIdempotent

The newest headlines from 70+ news sites, newest first, from every section or one. When the user names a topic, company or person, use search_news instead. With one_per_story (the default) each story appears once, as its newest article, and story_size says how many articles the story has. Each item is a headline, the publisher's own short description and the publisher's url: name the source and link the url when you show it.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoHow many articles to return (1 to 100).
categoryNoOnly this news section. Leave it out for every section.
one_per_storyNoOne article per story (true) or every article (false).

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
countYesHow many articles are in articles.
articlesYesNewest first.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "properties": {
+    "articles": {
+      "description": "Newest first.",
+      "items": {
+        "description": "One article.",
+        "properties": {
+          "category": {
+            "description": "The news section, e.g. world or tech.",
+            "type": "string"
+          },
+          "description": {
+            "description": "The publisher's own short description from its feed; null when the feed has none.",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "headline": {
+            "description": "The headline, as the publisher wrote it.",
+            "type": "string"
+          },
+          "id": {
+            "description": "The article's id.",
+            "type": "string"
+          },
+          "published_at": {
+            "description": "When the publisher published it, as an RFC 3339 time in UTC.",
+            "type": "string"
+          },
+          "source": {
+            "description": "The publisher's name.",
+            "type": "string"
+          },
+          "story_id": {
+            "description": "The story the article belongs to: pass it to story_coverage for every news site's coverage. null for an article not yet grouped into a story.",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "story_size": {
+            "description": "How many articles the story has. Present only when one_per_story is true.",
+            "type": "integer"
+          },
+          "url": {
+            "description": "The publisher's own article: link this when you show the headline.",
+            "type": "string"
+          }
+        },
+        "required": [
+          "id",
+          "headline",
+          "url",
+          "published_at",
+          "source",
+          "category",
+          "description",
+          "story_id"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "count": {
+      "description": "How many articles are in articles.",
+      "type": "integer"
+    }
+  },
+  "required": [
+    "count",
+    "articles"
+  ],
+  "type": "object"
+}
  2. First observed

TDQS

A4.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so safety is covered. The description adds genuine behavioral context beyond that: the one-per-story collapsing rule, what story_size reports, and the shape of each item (headline, publisher description, url). It stops short of describing pagination or how to page through results.

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?

Front-loaded with scope and ordering, then the routing rule, then output guidance. Every clause carries information; no filler.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/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 values needn't be re-explained, yet the description still says enough about item contents to set display expectations. Nothing needed to call this tool correctly is missing.

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 100% so the baseline is 3, but the description genuinely adds semantics: it explains that one_per_story defaults to collapsing multiple articles into one story and clarifies story_size's meaning. Category is only implied via 'every section or one', adding little beyond the enum.

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 ('newest headlines from 70+ news sites'), plus ordering ('newest first') and scope ('every section or one'). It explicitly distinguishes itself from the sibling search_news, 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 Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives an explicit routing rule: 'When the user names a topic, company or person, use search_news instead.' This names the alternative and the condition that selects it, which is exactly the when-to-use guidance an agent needs.

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

All Noozra 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