Pure Report — Neutral News

Trending news events

trending_events

Read-only

List the news events with the most current coverage activity. Each event clusters many outlets' articles about one story and includes headline (the published story's headline, else the event name), has_story (get_event returns Pure Report's neutral news story) and has_account (get_event also returns a sentence-cited account with verbatim receipts). Returns slugs to pass to get_event / compare_coverage.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`limit`	No	Max events, 1-25 (default 10).

Output Schema

TableJSON Schema

Name	Required	Description	Default
`events`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedOct 9, 2026
- addedOutput schema / properties / events / items / properties / has_story
```
Added value: +{
+  "type": "boolean"
+}
```
- addedOutput schema / properties / events / items / properties / headline
```
Added value: +{
+  "type": [
+    "string",
+    "null"
+  ]
+}
```

Changed1 schema field changedJul 13, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "events": {
+      "items": {
+        "properties": {
+          "article_count": {
+            "type": [
+              "integer",
+              "null"
+            ]
+          },
+          "first_seen": {
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "has_account": {
+            "type": "boolean"
+          },
+          "name": {
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "slug": {
+            "type": "string"
+          },
+          "url": {
+            "type": "string"
+          }
+        },
+        "type": "object"
+      },
+      "type": "array"
+    }
+  },
+  "required": [
+    "events"
+  ],
+  "type": "object"
+}

First observedJul 13, 2026

TDQS

A4.3/5.0

Behavior4/5

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

With only readOnlyHint=true in annotations, the description carries extra weight and does so: it explains that events aggregate many outlets' articles, decodes the headline fallback logic, and states what the has_story and has_account flags promise about get_event's response. It does not discuss pagination or result-volume behavior, but the chaining semantics are genuinely useful context beyond the annotation.

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, front-loaded with the core purpose, then field semantics, then the chaining target. Every clause conveys information an agent needs; nothing is padding or restated from the title.

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?

An output schema exists, so return structure need not be re-explained, yet the description still adds the flag semantics an agent needs to decide whether to follow up with get_event. For a single-optional-parameter, read-only list tool, nothing needed for correct invocation is missing.

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 coverage is 100% and the single limit parameter is fully described in the schema (range 1-25, default 10). The description adds no parameter-level detail, so the baseline 3 applies rather than a bonus.

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 a specific verb and resource ('List the news events with the most current coverage activity') and immediately qualifies the ranking criterion, which is what separates it from a plain search. The added definition of an event as a cluster of many outlets' articles about one story removes any ambiguity about what is being listed.

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?

It clearly frames the usage context (surfacing stories with the most current coverage activity) and gives explicit workflow guidance by naming the downstream tools get_event and compare_coverage for the returned slugs. It stops short of an explicit when-not or a direct comparison against the sibling search_news, so it is clear but not fully routing.

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

All Pure Report — Neutral 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?