Pure Report — Neutral News

Search neutral news

search_news

Read-only

Search Pure Report's neutral, bias-scored news. Returns articles with neutral summaries in our own words; bias_score (0-100) rates the ORIGINAL source reporting (0 = wire-neutral, 100 = advocacy), NOT the returned summary, which is neutral by design. Each result also lists the event(s) it belongs to — pass an event slug to get_event for the neutral writeup or compare_coverage for cross-outlet framing. Ranked by relevance and recency.

Input Schema

TableJSON Schema

Name	Required	Description
`limit`	No	Max results to RETURN, 1-40 (default 15). Does not affect total_matches, which always reports how many articles matched.
`query`	Yes	Keywords or phrase, e.g. "Iran sanctions" or "2026 election".
`topic`	No	Optional topic-slug filter. An unrecognized value searches all topics and returns a warning.
`offset`	No	Skip this many matches — page through results beyond the 40-row limit. The response echoes offset/returned/next_offset; next_offset is null on the last page.
`published_after`	No	Only articles published on/after this date. 'YYYY-MM-DD' or full ISO. Use with published_before to bound a period, e.g. coverage during June.
`published_before`	No	Only articles published on/before this date. 'YYYY-MM-DD' or full ISO.

Output Schema

TableJSON Schema

Name	Required	Description
`query`	Yes
`offset`	No
`results`	Yes
`warning`	No
`returned`	No
`next_offset`	No
`applied_topic`	No
`total_matches`	Yes	TOTAL articles matching the query, independent of `limit` — not the number returned. len(results) < total_matches means more exist.
`result_composition`	No	Factual description of what the returned set is ABOUT. Search is lexical, so every query term appears in every result; this reports whether a term is the SUBJECT (title/entities/lede) or only a body mention, plus the entity distribution. Measurements only — no verdict.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 9, 2026
- addedOutput schema / properties / results / items / properties / events / items / properties / headline
```
Added value: +{
+  "type": [
+    "string",
+    "null"
+  ]
+}
```

Changed6 schema fields changedAug 2, 2026

addedInput schema / properties / offset

Added value: +{
+  "description": "Skip this many matches — page through results beyond the 40-row limit. The response echoes offset/returned/next_offset; next_offset is null on the last page.",
+  "type": "integer"
+}

addedInput schema / properties / published_after

Added value: +{
+  "description": "Only articles published on/after this date. 'YYYY-MM-DD' or full ISO. Use with published_before to bound a period, e.g. coverage during June.",
+  "type": "string"
+}

addedInput schema / properties / published_before

Added value: +{
+  "description": "Only articles published on/before this date. 'YYYY-MM-DD' or full ISO.",
+  "type": "string"
+}

addedOutput schema / properties / next_offset

Added value: +{
+  "type": [
+    "integer",
+    "null"
+  ]
+}

addedOutput schema / properties / offset
```
Added value: +{
+  "type": "integer"
+}
```
addedOutput schema / properties / returned
```
Added value: +{
+  "type": "integer"
+}
```

Changed1 schema field changedAug 2, 2026

addedOutput schema / properties / result_composition

Added value: +{
+  "description": "Factual description of what the returned set is ABOUT. Search is lexical, so every query term appears in every result; this reports whether a term is the SUBJECT (title/entities/lede) or only a body mention, plus the entity distribution. Measurements only — no verdict.",
+  "type": "object"
+}

Changed2 schema fields changedAug 2, 2026

changedInput schema / properties / limit / description

Previous value: -"Max results, 1-40 (default 15)."New value: +"Max results to RETURN, 1-40 (default 15). Does not affect total_matches, which always reports how many articles matched."

addedOutput schema / properties / total_matches / description

Added value: +"TOTAL articles matching the query, independent of `limit` — not the number returned. len(results) < total_matches means more exist."

Changed1 schema field changedJul 13, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "applied_topic": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "query": {
+      "type": "string"
+    },
+    "results": {
+      "items": {
+        "properties": {
+          "bias_score": {
+            "type": [
+              "number",
+              "null"
+            ]
+          },
+          "events": {
+            "items": {
+              "properties": {
+                "name": {
+                  "type": [
+                    "string",
+                    "null"
+                  ]
+                },
+                "slug": {
+                  "type": "string"
+                }
+              },
+              "type": "object"
+            },
+            "type": "array"
+          },
+          "id": {
+            "type": "integer"
+          },
+          "published_at": {
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "source": {
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "summary": {
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "title": {
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "url": {
+            "type": "string"
+          }
+        },
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "total_matches": {
+      "type": "integer"
+    },
+    "warning": {
+      "type": "string"
+    }
+  },
+  "required": [
+    "query",
+    "total_matches",
+    "results"
+  ],
+  "type": "object"
+}

First observedJul 13, 2026

TDQS

A4.4/5.0

Behavior5/5

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

Beyond readOnlyHint=true, the description discloses behavior an agent could easily get wrong: bias_score rates the ORIGINAL source reporting (0=wire-neutral, 100=advocacy), NOT the neutral returned summary. It also discloses the ranking function (relevance and recency), which annotations do not cover.

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?

Four dense, front-loaded sentences with no filler; the core purpose leads and the disambiguation follows. The bias_score sentence is long but earns its place because it prevents a costly misinterpretation. Slightly heavy for a search tool, but no wasted clauses.

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 supplies the interpretive context the schema cannot (what bias_score means, that results carry event links). For a 6-parameter, read-only search tool, nothing an agent needs to call it correctly 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 description coverage is 100%, so every parameter (limit, query, topic, offset, dates) is already fully documented, and this is the baseline case per the rubric. The description adds no parameter-level detail (e.g. query syntax, topic slug format) beyond the schema; its narrative content is about return values, not inputs.

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?

Opens with a specific verb+resource ('Search Pure Report's neutral, bias-scored news') and immediately distinguishes what is returned ('articles with neutral summaries in our own words'). It also names the downstream siblings (get_event, compare_coverage) that consume an event slug, so an agent can place it in the workflow without opening other schemas.

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?

Gives clear context for when the tool is appropriate ('ranked by relevance and recency', event-linked results) and explicitly routes the agent onward: 'pass an event slug to get_event ... or compare_coverage'. It does not state when NOT to use it (e.g. browsing trending_events for undirected discovery), so it falls short of full alternative/exclusion guidance.

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?