Pollar News

List Pollar breaking-news moments

list_live_moments

Read-only

Lists Pollar's live and recently ended breaking-news moments. Use to discover what is breaking now or what ended within the past 24 hours. Each moment carries story metadata (storyId, chapterIndex) when it belongs to a multi-chapter story — chapters of the same continuing narrative are returned in chapter order. Pass a returned id to get_live_moment for the current snapshot.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`locale`	No		en

Output Schema

TableJSON Schema

Name	Required	Description	Default
`moments`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed5 schema fields changedJun 19, 2026

addedOutput schema / properties / moments / items / properties / chapterIndex
```
Added value: +{
+  "type": "number"
+}
```

addedOutput schema / properties / moments / items / properties / decisionAt

Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ]
+}

addedOutput schema / properties / moments / items / properties / eventOnsetAt

Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ]
+}

addedOutput schema / properties / moments / items / properties / freshnessBand

Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ]
+}

addedOutput schema / properties / moments / items / properties / storyId
```
Added value: +{
+  "type": "string"
+}
```

Changed1 schema field changedJun 19, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": false,
+  "properties": {
+    "moments": {
+      "items": {
+        "additionalProperties": false,
+        "properties": {
+          "endedAt": {
+            "anyOf": [
+              {
+                "type": "string"
+              },
+              {
+                "type": "null"
+              }
+            ]
+          },
+          "id": {
+            "type": "string"
+          },
+          "importance": {
+            "type": "number"
+          },
+          "kind": {
+            "type": "string"
+          },
+          "lastBody": {
+            "type": "string"
+          },
+          "lastStateAt": {
+            "type": "string"
+          },
+          "startedAt": {
+            "type": "string"
+          },
+          "status": {
+            "enum": [
+              "live",
+              "ended"
+            ],
+            "type": "string"
+          },
+          "title": {
+            "type": "string"
+          }
+        },
+        "required": [
+          "id",
+          "kind",
+          "status",
+          "title",
+          "startedAt"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    }
+  },
+  "required": [
+    "moments"
+  ],
+  "type": "object"
+}

First observedJun 18, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Beyond readOnlyHint annotation, description adds temporal scope (past 24 hours), chapter ordering, and relationship to get_live_moment. No contradictions.

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?

Three sentences, front-loaded with main action. Every sentence adds necessary context without fluff.

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?

Tool is simple (1 optional param, read-only). Description covers return content (story metadata, chapter order) and references further action. Complete for this tool.

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

Parameters2/5

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

Schema has 1 param (locale) with 0% description coverage. Description does not mention locale at all, missing opportunity to explain filtering or default behavior. Parameter is simple but description should compensate.

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?

Clearly states it lists live and recently ended breaking-news moments. Distinguishes by specifying temporal scope (within 24 hours) and mentions story metadata and chapter ordering, differentiating from siblings like get_live_moment or list_live_stories.

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?

Explicitly says to use for discovering breaking news now or recently ended. Recommends passing id to get_live_moment for detail. Does not explicitly contrast with siblings like list_live_stories, but context is clear.

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

All Pollar News 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.

Resources

Need Help?