Pollar News

Get a Pollar thread

get_thread

Read-only

Fetches a single Pollar thread by slug (from list_threads): its thesis, current state-of-play, and recent chronicle entries with citations. Set withHistory=true to also include how the thesis evolved over time. Returns the thread detail with a canonical url.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`slug`	Yes	Thread slug, e.g. 'demokracje-populizm'
`locale`	No		en
`withHistory`	No

Output Schema

TableJSON Schema

Name	Required	Description	Default
`id`	Yes
`url`	Yes
`name`	Yes
`thesis`	Yes
`entries`	Yes
`history`	No
`section`	Yes
`entryCount`	Yes
`lastTickAt`	Yes
`stateOfPlay`	Yes
`weekHighlights`	Yes
`changeMagnitude`	Yes
`magnitudeReason`	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": {
+    "changeMagnitude": {
+      "anyOf": [
+        {
+          "type": "number"
+        },
+        {
+          "type": "null"
+        }
+      ]
+    },
+    "entries": {
+      "items": {
+        "additionalProperties": false,
+        "properties": {
+          "body": {
+            "type": "string"
+          },
+          "citations": {
+            "items": {
+              "additionalProperties": false,
+              "properties": {
+                "domain": {
+                  "type": "string"
+                },
+                "title": {
+                  "type": "string"
+                },
+                "url": {
+                  "format": "uri",
+                  "type": "string"
+                }
+              },
+              "required": [
+                "url",
+                "title",
+                "domain"
+              ],
+              "type": "object"
+            },
+            "type": "array"
+          },
+          "headline": {
+            "type": "string"
+          },
+          "occurredAt": {
+            "type": "string"
+          },
+          "significance": {
+            "type": "boolean"
+          }
+        },
+        "required": [
+          "occurredAt",
+          "headline",
+          "body",
+          "citations"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "entryCount": {
+      "type": "number"
+    },
+    "history": {
+      "items": {
+        "additionalProperties": false,
+        "properties": {
+          "changeMagnitude": {
+            "type": "number"
+          },
+          "magnitudeReason": {
+            "anyOf": [
+              {
+                "type": "string"
+              },
+              {
+                "type": "null"
+              }
+            ]
+          },
+          "stateOfPlay": {
+            "type": "string"
+          },
+          "thesis": {
+            "type": "string"
+          },
+          "tickAt": {
+            "type": "string"
+          },
+          "trigger": {
+            "enum": [
+              "scheduled",
+              "signal",
+              "manual"
+            ],
+            "type": "string"
+          }
+        },
+        "required": [
+          "tickAt",
+          "thesis",
+          "stateOfPlay",
+          "changeMagnitude",
+          "magnitudeReason",
+          "trigger"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "id": {
+      "type": "string"
+    },
+    "lastTickAt": {
+      "anyOf": [
+        {
+          "type": "string"
+        },
+        {
+          "type": "null"
+        }
+      ]
+    },
+    "magnitudeReason": {
+      "anyOf": [
+        {
+          "type": "string"
+        },
+        {
+          "type": "null"
+        }
+      ]
+    },
+    "name": {
+      "type": "string"
+    },
+    "section": {
+      "enum": [
+        "europe",
+        "world",
+        "other"
+      ],
+      "type": "string"
+    },
+    "stateOfPlay": {
+      "anyOf": [
+        {
+          "type": "string"
+        },
+        {
+          "type": "null"
+        }
+      ]
+    },
+    "thesis": {
+      "type": "string"
+    },
+    "url": {
+      "format": "uri",
+      "type": "string"
+    },
+    "weekHighlights": {
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    }
+  },
+  "required": [
+    "id",
+    "section",
+    "name",
+    "thesis",
+    "changeMagnitude",
+    "magnitudeReason",
+    "lastTickAt",
+    "entryCount",
+    "url",
+    "stateOfPlay",
+    "weekHighlights",
+    "entries"
+  ],
+  "type": "object"
+}

First observedJun 18, 2026

TDQS

A4.5/5.0

Behavior4/5

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

Annotations declare readOnlyHint=true, confirming no destructive action. The description adds beyond annotations by detailing what the response includes (canonical url, chronicle entries) and how withHistory affects the data (thesis evolution). It is consistent with the read-only nature.

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: first states main purpose, second explains key parameter, third describes output. No wasted words, front-loaded with actions, and effective for fast scanning.

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?

Given the tool's simplicity and the presence of an output schema (defined externally), the description covers all essential aspects: what is fetched, how to use it (slug), and optional behavior (withHistory). No gaps remain for agent understanding.

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 already describes slug (with example), locale (enum/default), and withHistory (default). Description adds value by connecting slug to list_threads (source), and explaining withHistory's effect ('how the thesis evolved over time'), which is not in schema. Since schema coverage is 100% in terms of descriptions, baseline is 3, but the added context elevates it.

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 clearly states it fetches a single Pollar thread by slug and lists the components (thesis, state-of-play, chronicle entries). It distinguishes from sibling tools like list_threads by specifying 'from list_threads' and from other entity getters (e.g., get_event, get_live_moment) by targeting threads.

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 implies usage after list_threads (citing 'from list_threads') and mentions the optional withHistory parameter for evolutionary detail. Although it does not explicitly exclude other tools, the context and sibling tool names make it clear that this is for retrieving a single thread by slug.

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?