Pure Report — Neutral News

Neutral event writeup

get_event

Read-only

Get the full neutral writeup of one news event by slug: 'story', Pure Report's own neutral news story (headline + paragraphs, written from the outlets' reports and checked before publishing); 'account', a sentence-cited breakdown (lede, what-we-know bullets with verbatim source receipts, single-source attributed items) when one passed its gates; and a coverage census (how many outlets by political lean, earliest report). Either writeup may be null; the census is always returned.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`slug`	Yes	Event slug from trending_events or a search_news result, e.g. "tyler-robinson-trial-for-charlie-kirk-murder".

Output Schema

TableJSON Schema

Name	Required	Description	Default
`url`	Yes
`name`	No
`slug`	Yes
`story`	No
`status`	No
`account`	No
`coverage`	Yes
`headline`	No
`first_seen`	No
`account_note`	No
`article_count`	No
`coverage_report`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedOct 9, 2026

addedOutput schema / properties / headline

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

addedOutput schema / properties / story

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

Changed1 schema field changedAug 2, 2026
- addedOutput schema / properties / coverage_report
```
Added value: +{
+  "type": [
+    "object",
+    "null"
+  ]
+}
```

Changed1 schema field changedJul 13, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "account": {
+      "type": [
+        "object",
+        "null"
+      ]
+    },
+    "account_note": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "article_count": {
+      "type": [
+        "integer",
+        "null"
+      ]
+    },
+    "coverage": {
+      "type": "object"
+    },
+    "first_seen": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "name": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "slug": {
+      "type": "string"
+    },
+    "status": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "url": {
+      "type": "string"
+    }
+  },
+  "required": [
+    "slug",
+    "coverage",
+    "url"
+  ],
+  "type": "object"
+}

First observedJul 13, 2026

TDQS

A3.5/5.0

Behavior3/5

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

Annotations only declare readOnlyHint=true, so safety is covered, and the description does usefully disclose that story/account may be null while the census is always returned. However, an output schema already exists to carry return-value detail, and there is no mention of auth, rate limits, or freshness/latency behavior.

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?

One long semicolon-delimited sentence, but the core action is front-loaded before the component breakdown. Dense jargon ('gates', 'receipts') adds weight without much payback, yet nothing is wasted enough to undermine it.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/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 explain structure, and it sensibly summarizes the three payload parts and their nullability. Coverage is nearly complete for a single-parameter read tool; only the sibling-selection guidance 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?

Only one parameter and schema description coverage is 100%, with the schema already supplying format guidance and a concrete example slug. The description adds nothing beyond 'by slug', so the baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource — 'Get the full neutral writeup of one news event by slug' — and enumerates the three returned components (story, account, census). It implies differentiation from get_article by stressing the writeup is 'Pure Report's own', but never names a sibling, so an agent still has to infer which of get_event/get_article/compare_coverage applies.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is only implied: pass an event slug, receive a writeup. There is no explicit when-to-use versus get_article or compare_coverage, and no stated prerequisites or exclusions. The null-handling note ('either writeup may be null') is the closest thing to operational 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?