CLSTR

Top developing situations

get_top_situations

Read-onlyIdempotent

List the situations developing now, ranked by relevance: a blend of significance, how many outlets are covering it, and how recently it moved. So a lower significance score can rank above a higher one, and that ordering is intentional; do not re-sort. A situation is an ongoing storyline that groups related news events over time and carries a maintained summary and a source count (how many outlets are behind it). Optionally filter by category, by country, and by time window (24h, 7d, or 30d), and switch the ordering to newest activity first with sort. Use this to answer 'what is going on in the world', 'what is happening in ' or 'what is happening in ' when there is no specific topic yet, then open any result with get_situation_timeline. When there are more, the result ends with a cursor to page further. Pass summary: "full" to get each situation's maintained summary in full, instead of a one-line preview, without a follow-up call per result; full summaries in a list are not enabled for every account, so read summary_mode in the result to see what you got, and use get_situation_timeline for one situation's summary in full. Results carry canonical clstr.news links.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_top_situations"
  }
}

Input Schema

Name	Required	Description
`sort`	No	Ordering. 'relevance' (the default) blends significance, source count and recency; 'recent' is newest activity first.
`limit`	No	Max situations to return. Default 15.
`cursor`	No	From a previous result, to page further. Pass the same filters alongside it: a cursor resumes only under the filter set that produced it.
`window`	No	Time window. Default '7d'.
`country`	No	Optional country filter: comma-separated ISO 3166-1 alpha-2 codes, for example "US,GB". Up to 10 at once. A situation matches if any of them is among the countries most directly involved in it.
`summary`	No	How much summary text each row carries. 'preview' (the default) is a one-line preview; 'full' returns the maintained summary in full, so you do not need a follow-up call per result. On get_top_situations, 'full' is not enabled for every account: read `summary_mode` in the result to see which mode was actually served, and get_situation_timeline always returns one situation's summary in full. 'full' returns each situation's full summary, up to roughly 300 words per row, so keep limit small when you use it.
`category`	No	Optional category filter.

Output Schema

Name	Required	Description
`data`	Yes
`next_cursor`	Yes	Pass back as cursor to page further. Null at the end.
`window_days`	Yes	The time window this result covers, in days, which is not always the one requested.
`summary_mode`	Yes	The summary mode this result was served in, which is not always the one requested.

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedOct 30, 2026

changedInput schema / properties / country / description

Previous value: -"Optional country filter: comma-separated ISO 3166-1 alpha-2 codes, for example \"US,GB\". Up to 10 at once. A situation matches if it is covered in any of them."New value: +"Optional country filter: comma-separated ISO 3166-1 alpha-2 codes, for example \"US,GB\". Up to 10 at once. A situation matches if any of them is among the countries most directly involved in it."

changedInput schema / properties / summary / description

Previous value: -"How much summary text each row carries. 'preview' (the default) is a one-line preview; 'full' returns the maintained summary in full, so you do not need a follow-up call per result. On get_top_situations, 'full' is not enabled for every account: read `summary_mode` in the result to see which mode was actually served, and get_situation_timeline always returns one situation's summary in full. 'full' returns each situation's complete summary, up to roughly 300 words per row, so keep limit small when you use it."New value: +"How much summary text each row carries. 'preview' (the default) is a one-line preview; 'full' returns the maintained summary in full, so you do not need a follow-up call per result. On get_top_situations, 'full' is not enabled for every account: read `summary_mode` in the result to see which mode was actually served, and get_situation_timeline always returns one situation's summary in full. 'full' returns each situation's full summary, up to roughly 300 words per row, so keep limit small when you use it."

Changed1 schema field changedOct 28, 2026
- changedOutput schema / properties / data / items / properties / url / description
```
Previous value: -"Canonical clstr.news URL. Cite this."New value: +"Canonical clstr.news URL."
```

Changed2 schema fields changedSep 24, 2026

addedOutput schema / properties / window_days

Added value: +{
+  "description": "The time window this result covers, in days, which is not always the one requested.",
+  "minimum": 1,
+  "type": "integer"
+}

changedOutput schema / required

Previous value: -[
-  "data",
-  "next_cursor",
-  "summary_mode"
-]New value: +[
+  "data",
+  "next_cursor",
+  "summary_mode",
+  "window_days"
+]

Changed4 schema fields changedSep 18, 2026

addedInput schema / properties / summary

Added value: +{
+  "description": "How much summary text each row carries. 'preview' (the default) is a one-line preview; 'full' returns the maintained summary in full, so you do not need a follow-up call per result. On get_top_situations, 'full' is not enabled for every account: read `summary_mode` in the result to see which mode was actually served, and get_situation_timeline always returns one situation's summary in full. 'full' returns each situation's complete summary, up to roughly 300 words per row, so keep limit small when you use it.",
+  "enum": [
+    "preview",
+    "full"
+  ],
+  "type": "string"
+}

addedOutput schema / properties / data / items / properties / summary

Added value: +{
+  "description": "The maintained situation summary, in full. Present only when summary: \"full\" was requested.",
+  "type": "string"
+}

addedOutput schema / properties / summary_mode

Added value: +{
+  "description": "The summary mode this result was served in, which is not always the one requested.",
+  "enum": [
+    "preview",
+    "full"
+  ],
+  "type": "string"
+}

changedOutput schema / required

Previous value: -[
-  "data",
-  "next_cursor"
-]New value: +[
+  "data",
+  "next_cursor",
+  "summary_mode"
+]

Changed4 schema fields changedSep 15, 2026

addedInput schema / properties / country

Added value: +{
+  "description": "Optional country filter: comma-separated ISO 3166-1 alpha-2 codes, for example \"US,GB\". Up to 10 at once. A situation matches if it is covered in any of them.",
+  "maxLength": 200,
+  "type": "string"
+}

changedInput schema / properties / cursor / description

Previous value: -"From a previous result, to page further. Pass the same window and category alongside it."New value: +"From a previous result, to page further. Pass the same filters alongside it: a cursor resumes only under the filter set that produced it."

addedInput schema / properties / sort

Added value: +{
+  "description": "Ordering. 'relevance' (the default) blends significance, source count and recency; 'recent' is newest activity first.",
+  "enum": [
+    "relevance",
+    "recent"
+  ],
+  "type": "string"
+}

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "data": {
+      "items": {
+        "properties": {
+          "categories": {
+            "items": {
+              "type": "string"
+            },
+            "type": "array"
+          },
+          "category": {
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "cluster_count": {
+            "minimum": 0,
+            "type": "integer"
+          },
+          "countries": {
+            "description": "ISO 3166-1 alpha-2 codes.",
+            "items": {
+              "type": "string"
+            },
+            "type": "array"
+          },
+          "first_seen": {
+            "description": "ISO-8601 UTC timestamp.",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "id": {
+            "type": "string"
+          },
+          "last_updated": {
+            "description": "ISO-8601 UTC timestamp.",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "latest_cluster_title": {
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "significance_score": {
+            "description": "AI-generated significance, 1 to 10, where 8 and above is exceptional.",
+            "type": [
+              "integer",
+              "null"
+            ]
+          },
+          "slug": {
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "source_count": {
+            "minimum": 0,
+            "type": "integer"
+          },
+          "status": {
+            "description": "ACTIVE or QUIET.",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "summary_preview": {
+            "type": "string"
+          },
+          "title": {
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "url": {
+            "description": "Canonical clstr.news URL. Cite this.",
+            "type": "string"
+          }
+        },
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "next_cursor": {
+      "description": "Pass back as cursor to page further. Null at the end.",
+      "type": [
+        "string",
+        "null"
+      ]
+    }
+  },
+  "required": [
+    "data",
+    "next_cursor"
+  ],
+  "type": "object"
+}

First observedAug 20, 2026

TDQS

A4.8/5.0

Behavior5/5

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

Goes well beyond the readOnly/idempotent annotations: it discloses that the ordering is intentional and must not be re-sorted, that paging is cursor-based with filters needing to match, that summary: 'full' is not enabled for every account and summary_mode in the result should be read, and that results carry canonical clstr.news links. These are non-obvious behaviors an agent would otherwise get wrong.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with the core action, ranking model, and the definition of a situation before filters and caveats. It is dense and mostly earns its length, though the ranking explanation is slightly verbose ('a blend of significance, how many outlets are covering it, and how recently it moved').

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?

With an output schema present, the description needn't document return fields, yet it still covers summary_mode, cursor pagination, and the link format. For a seven-parameter, multi-filter list tool this leaves no ambiguity about how to call it or interpret the result.

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 would be 3; the description adds real meaning by explaining the relevance blend, the sort switch, cursor resumption semantics, and the per-row word cost of summary: 'full'. It doesn't re-specify the country/category enum semantics beyond the schema, so it stops short of 5.

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 the specific verb and resource ('List the situations developing now') and immediately defines what a situation is, including its maintained summary and source count. The ranking model and the intentional blend of significance/source count/recency distinguish it from get_situation_timeline and search_situations, which are named as follow-ups or alternatives.

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 concrete when-to-use triggers ('what is going on in the world', 'what is happening in <category>', 'what is happening in <country>' when no specific topic exists) and explicitly routes detail-seekers to get_situation_timeline. It also covers when to use summary: 'full' versus a follow-up call, and warns to keep limit small in that mode.

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

All CLSTR 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?