Pollar News

Get a Pollar news event

get_event

Read-only

Fetches the full Pollar coverage of a single event by its slug (get slugs from search_news or list_top_news). Returns title, lead, full summary, source citations, mentioned people, locations, charts, and a canonical pollar.news url to cite.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`slug`	Yes	Event slug (per-locale)
`locale`	No		en

Output Schema

TableJSON Schema

Name	Required	Description	Default
`id`	Yes
`url`	Yes
`lead`	Yes
`slug`	Yes
`title`	Yes
`charts`	Yes
`sources`	Yes
`summary`	Yes
`imageUrl`	Yes
`locations`	Yes
`modifiedAt`	Yes
`imageSource`	Yes
`publishedAt`	Yes
`categoryPath`	Yes
`mentionedPeople`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedJun 19, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": false,
+  "properties": {
+    "categoryPath": {
+      "items": [
+        {
+          "type": "string"
+        },
+        {
+          "type": "string"
+        },
+        {
+          "type": "string"
+        }
+      ],
+      "type": "array"
+    },
+    "charts": {
+      "items": {},
+      "type": "array"
+    },
+    "id": {
+      "type": "string"
+    },
+    "imageSource": {
+      "type": "string"
+    },
+    "imageUrl": {
+      "type": "string"
+    },
+    "lead": {
+      "type": "string"
+    },
+    "locations": {
+      "items": {},
+      "type": "array"
+    },
+    "mentionedPeople": {
+      "items": {},
+      "type": "array"
+    },
+    "modifiedAt": {
+      "type": "string"
+    },
+    "publishedAt": {
+      "type": "string"
+    },
+    "slug": {
+      "type": "string"
+    },
+    "sources": {
+      "items": {
+        "additionalProperties": false,
+        "properties": {
+          "publishDate": {
+            "type": "string"
+          },
+          "source": {
+            "type": "string"
+          },
+          "title": {
+            "type": "string"
+          },
+          "url": {
+            "format": "uri",
+            "type": "string"
+          }
+        },
+        "required": [
+          "title",
+          "url",
+          "source"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "summary": {
+      "type": "string"
+    },
+    "title": {
+      "type": "string"
+    },
+    "url": {
+      "format": "uri",
+      "type": "string"
+    }
+  },
+  "required": [
+    "id",
+    "slug",
+    "title",
+    "lead",
+    "summary",
+    "categoryPath",
+    "locations",
+    "mentionedPeople",
+    "charts",
+    "sources",
+    "imageUrl",
+    "imageSource",
+    "publishedAt",
+    "modifiedAt",
+    "url"
+  ],
+  "type": "object"
+}

First observedJun 18, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Annotations declare readOnlyHint=true; description details returned fields (title, lead, summary, citations, etc.), adding rich behavioral context without contradicting annotations.

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?

Two sentences, front-loaded with purpose and source of slug, no wasted words.

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?

With output schema present, description adequately covers input context and return content; minor omission of constraints or error cases, but sufficient given tool simplicity.

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 describes slug and locale; description adds crucial context that slugs originate from search/list tools, and lists output fields (not parameters), improving understanding beyond schema 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?

Clearly states it fetches full coverage of a single event by slug, lists returned content types, and directs to sibling tools for obtaining slugs, distinguishing its scope from search/list tools.

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 states when to use (to get a single event's full coverage using a slug from search/list tools), providing clear context for selection among siblings, though no explicit 'when not to use' is given.

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?