Pollar News

Get a breaking-news moment snapshot

get_live_moment

Read-only

Fetches the current snapshot of a breaking-news moment by id, including ordered updates and a source summary. Accepts either a moment id or a story id; story ids resolve to the latest chapter of that story. This is a point-in-time read rather than a stream. Wait at least 30 seconds before refreshing.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`id`	Yes
`locale`	No		en

Output Schema

TableJSON Schema

Name	Required	Description	Default
`moment`	Yes
`states`	Yes
`sourcesSummary`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed5 schema fields changedJun 19, 2026

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

addedOutput schema / properties / moment / properties / decisionAt

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

addedOutput schema / properties / moment / properties / eventOnsetAt

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

addedOutput schema / properties / moment / properties / freshnessBand

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

addedOutput schema / properties / moment / 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": {
+    "moment": {
+      "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"
+    },
+    "sourcesSummary": {
+      "additionalProperties": false,
+      "properties": {
+        "countries": {
+          "items": {
+            "type": "string"
+          },
+          "type": "array"
+        },
+        "totalUrls": {
+          "type": "number"
+        }
+      },
+      "required": [
+        "totalUrls",
+        "countries"
+      ],
+      "type": "object"
+    },
+    "states": {
+      "items": {
+        "additionalProperties": false,
+        "properties": {
+          "body": {
+            "type": "string"
+          },
+          "createdAt": {
+            "type": "string"
+          },
+          "importance": {
+            "type": "number"
+          },
+          "kind": {
+            "type": "string"
+          },
+          "pinned": {
+            "type": "boolean"
+          }
+        },
+        "required": [
+          "kind",
+          "importance",
+          "body",
+          "pinned",
+          "createdAt"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    }
+  },
+  "required": [
+    "moment",
+    "states",
+    "sourcesSummary"
+  ],
+  "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?

Annotations declare readOnlyHint=true, and the description adds that it is a 'point-in-time read' and not a stream, plus the refresh delay. This aligns with annotations and provides additional behavioral context beyond what annotations offer.

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?

Four sentences, each purposeful. The first sentence states the core action and output. The second clarifies the input flexibility. The third and fourth provide essential behavioral guidance. No filler or redundancy.

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?

The output schema exists, so return values are covered. The description adds what the snapshot includes (ordered updates, source summary) and explains ID resolution and refresh behavior. This is sufficient for a read-only tool with an output schema, but could mention the locale parameter briefly.

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 0%, so the description must add meaning. It explains that the id parameter can be a moment ID or story ID, adding semantic context. However, the locale parameter is not mentioned, leaving some parameter behavior unexplained.

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?

The description starts with a specific verb ('Fetches') and resource ('breaking-news moment snapshot'), clearly defines what is included (ordered updates, source summary), and distinguishes from siblings by mentioning it accepts moment or story IDs and is a point-in-time read versus a stream.

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?

The description provides clear context: it is a point-in-time read, not a stream, and advises waiting 30 seconds before refreshing. It also explains that story IDs resolve to the latest chapter. However, it does not explicitly state when to use this tool vs. alternatives like get_live_story or list_live_moments.

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?