Skip to main content
Glama

CLSTR

by news.clstr.mcp
OverviewDiscussionsAdmin

Top developing situations

get_top_situations
Read-onlyIdempotent

List the situations developing right 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. Cite the returned URLs.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
sortNoOrdering. 'relevance' (the default) blends significance, source count and recency; 'recent' is newest activity first.
limitNoMax situations to return. Default 15.
cursorNoFrom a previous result, to page further. Pass the same filters alongside it: a cursor resumes only under the filter set that produced it.
windowNoTime window. Default '7d'.
countryNoOptional 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.
summaryNoHow 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.
categoryNoOptional category filter.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
dataYes
next_cursorYesPass back as cursor to page further. Null at the end.
window_daysYesThe time window this result covers, in days, which is not always the one requested.
summary_modeYesThe summary mode this result was served in, which is not always the one requested.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • 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"
+]
  2. Changed4 schema fields changed
    • 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"
+]
  3. Changed4 schema fields changed
    • 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"
+}
  4. First observed

TDQS

A4.9/5.0
Behavior5/5

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

Beyond the readOnly/idempotent annotations, the description discloses non-obvious behavior: the blended relevance ranking is intentional and should not be re-sorted, cursor paging requires the same filters, and summary: "full" may not be enabled for every account so summary_mode must be read. This is meaningful context the annotations do not provide.

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?

The description is long but dense and front-loaded with the core purpose before filters, use cases, pagination, and caveats. Each sentence adds useful operational detail, with no filler or tautology.

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 seven optional parameters, annotations, and an output schema, the description covers the remaining operational essentials: when to use it, what the ordering means, how paging works, the summary_mode caveat, and the follow-up tool. An agent has enough to call it correctly without needing more.

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 is 3, but the description adds real parameter context: it explains how relevance is computed, that low significance can rank high, and that full summaries can be heavy and may fall back based on account entitlement. This goes beyond the schema's per-parameter descriptions.

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 opens with a specific verb and resource: 'List the situations developing right now, ranked by relevance', then defines what a situation is, so an agent knows exactly what is returned. It also differentiates from siblings by positioning this as the no-specific-topic list and routing follow-ups to get_situation_timeline.

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?

It gives explicit invocation triggers: 'Use this to answer "what is going on in the world"... when there is no specific topic yet', and indicates the alternative by saying to open results with get_situation_timeline. This makes when-to-use vs alternatives reasonably clear.

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

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