Pure Report — Neutral News

Get article

get_article

Read-only

Fetch one article by id: neutral rewritten title + body, a bias_score for the ORIGINAL source (not the rewrite), source, extracted entities, and the events it belongs to.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`article_id`	Yes	Numeric article id (from search_news results).

Output Schema

TableJSON Schema

Name	Required	Description	Default
`id`	Yes
`url`	Yes
`title`	No
`events`	No
`content`	No
`summary`	No
`entities`	No
`bias_score`	No
`source_url`	No
`source_name`	No
`published_at`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedAug 2, 2026
- addedOutput schema / properties / events
```
Added value: +{
+  "type": "array"
+}
```
- removedOutput schema / properties / narratives
```
Removed value: -{
-  "type": "array"
-}
```

Changed1 schema field changedJul 13, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "bias_score": {
+      "type": [
+        "number",
+        "null"
+      ]
+    },
+    "content": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "entities": {
+      "type": [
+        "object",
+        "array",
+        "null"
+      ]
+    },
+    "id": {
+      "type": "integer"
+    },
+    "narratives": {
+      "type": "array"
+    },
+    "published_at": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "source_name": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "source_url": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "summary": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "title": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "url": {
+      "type": "string"
+    }
+  },
+  "required": [
+    "id",
+    "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?

Beyond the readOnlyHint annotation, the description adds a key behavioral nuance: the bias_score refers to the ORIGINAL source, not the neutral rewrite. It also discloses the exact set of returned components, which prevents misinterpretation.

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 a single sentence that is information-dense without fluff. It lists the return fields in a structured way, making it easy to scan.

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?

For a simple one-parameter tool with an output schema and read-only annotation, the description covers the essential semantics and return contents. No critical gaps remain.

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 the parameter is already well-documented. The description does not add additional parameter details beyond restating 'by id', so baseline 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 fetches one article by id and enumerates the returned fields (neutral rewritten title+body, bias_score, source, entities, events). This specific verb+resource combo distinguishes it from siblings like search_news and get_event.

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 context is clear: use this when you have a specific article id (from search_news, per schema) and need full article details. It does not explicitly mention when not to use it or list alternatives, but the reading is unambiguous.

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?