Pure Report — Neutral News

Neutral event writeup

get_event

Read-only

Get the full neutral writeup of one news event by slug: a verification-gated account (lede, what-we-know bullets with verbatim source receipts, single-source attributed items) plus a coverage census (how many outlets by political lean, earliest report). If no gated account exists yet, the coverage census is still 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
`status`	No
`account`	No
`coverage`	Yes
`first_seen`	No
`account_note`	No
`article_count`	No
`coverage_report`	No

Schema Changelog

Changes observed during successful MCP inspections.

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

A4.3/5.0

Behavior4/5

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

Annotations provide readOnlyHint=true, so the description adds value by explaining the internal structure of the writeup and the fallback behavior when no gated account exists yet. This goes beyond the safety annotation and gives useful behavioral context without contradicting it.

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 two sentences, front-loaded with the main purpose, and every sentence adds value: the first details content, the second clarifies fallback. No fluff or redundancy.

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?

Given the output schema exists, the description sufficiently covers the tool's behavior: what the writeup contains, what the coverage census includes, and what happens if the gated account isn't ready. It is complete for a moderately complex tool and leaves no major gaps.

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?

The input schema already provides a thorough description of the slug parameter, including its source and an example (100% coverage). The description adds no new parameter semantics beyond repeating 'by slug', so the baseline score of 3 is appropriate.

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 clearly states the tool gets the full neutral writeup of one news event by slug, specifying the content (verification-gated account with lede, what-we-know bullets, receipts, attributed items) and the coverage census. This distinguishes it from siblings like get_article (likely raw article) and search_news (search). The verb and resource are specific and unambiguous.

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?

The description implies usage context by specifying the slug comes from trending_events or search_news, and explains what to expect. However, it doesn't explicitly state when to prefer this tool over alternatives (e.g., when needing verification-gated coverage vs. raw article), nor does it mention exclusions. This is clear context but lacks explicit alternative 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?