Spacenews

Get Articles

get_articles

Read-onlyIdempotent

Fetch the latest spaceflight news articles sorted by publication date. Returns title, summary, URL, image, and source.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`limit`	No	Number of articles to return (default 10, max 100)

Output Schema

TableJSON Schema

Name	Required	Description
`total`	Yes	Total number of articles available
`articles`	Yes
`returned`	Yes	Number of articles returned in this response

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedMay 24, 2026

addedInput schema / examples

Added value: +[
+  {
+    "limit": 10
+  },
+  {
+    "limit": 25
+  }
+]

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "articles": {
+      "items": {
+        "properties": {
+          "id": {
+            "description": "Article ID",
+            "type": "number"
+          },
+          "image_url": {
+            "description": "Article image URL",
+            "type": "string"
+          },
+          "published_at": {
+            "description": "Publication date (ISO 8601)",
+            "type": "string"
+          },
+          "source": {
+            "description": "News site source",
+            "type": "string"
+          },
+          "summary": {
+            "description": "Article summary",
+            "type": "string"
+          },
+          "title": {
+            "description": "Article title",
+            "type": "string"
+          },
+          "url": {
+            "description": "Article URL",
+            "type": "string"
+          }
+        },
+        "required": [
+          "id",
+          "title",
+          "summary",
+          "url",
+          "image_url",
+          "source",
+          "published_at"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "returned": {
+      "description": "Number of articles returned in this response",
+      "type": "number"
+    },
+    "total": {
+      "description": "Total number of articles available",
+      "type": "number"
+    }
+  },
+  "required": [
+    "total",
+    "returned",
+    "articles"
+  ],
+  "type": "object"
+}

Changed2 schema fields changedMay 13, 2026

removedInput schema / examples

Removed value: -[
-  {
-    "limit": 10,
-    "tag": "javascript"
-  },
-  {
-    "limit": 20,
-    "tag": "python",
-    "top": 7
-  }
-]

changedOutput schema / (root)

Previous value: -{
-  "properties": {
-    "articles": {
-      "description": "List of article summaries",
-      "items": {
-        "properties": {
-          "author": {
-            "description": "Article author information",
-            "properties": {
-              "name": {
-                "description": "Author full name",
-                "type": "string"
-              },
-              "username": {
-                "description": "Author username",
-                "type": "string"
-              }
-            },
-            "type": [
-              "object",
-              "null"
-            ]
-          },
-          "comments": {
-            "description": "Count of comments",
-            "type": "number"
-          },
-          "description": {
-            "description": "Article description or excerpt",
-            "type": [
-              "string",
-              "null"
-            ]
-          },
-          "id": {
-            "description": "Article numeric ID",
-            "type": "number"
-          },
-          "published_at": {
-            "description": "Publication timestamp (ISO 8601 format)",
-            "type": [
-              "string",
-              "null"
-            ]
-          },
-          "reactions": {
-            "description": "Count of public reactions",
-            "type": "number"
-          },
-          "reading_time_minutes": {
-            "description": "Estimated reading time in minutes",
-            "type": "number"
-          },
-          "tags": {
-            "description": "List of tags associated with article",
-            "items": {
-              "type": "string"
-            },
-            "type": "array"
-          },
-          "title": {
-            "description": "Article title",
-            "type": "string"
-          },
-          "url": {
-            "description": "Article URL",
-            "type": "string"
-          }
-        },
-        "required": [
-          "id",
-          "title",
-          "description",
-          "url",
-          "published_at",
-          "tags",
-          "reading_time_minutes",
-          "reactions",
-          "comments",
-          "author"
-        ],
-        "type": "object"
-      },
-      "type": "array"
-    }
-  },
-  "required": [
-    "articles"
-  ],
-  "type": "object"
-}New value: +null

Changed1 schema field changedMay 8, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "articles": {
+      "description": "List of article summaries",
+      "items": {
+        "properties": {
+          "author": {
+            "description": "Article author information",
+            "properties": {
+              "name": {
+                "description": "Author full name",
+                "type": "string"
+              },
+              "username": {
+                "description": "Author username",
+                "type": "string"
+              }
+            },
+            "type": [
+              "object",
+              "null"
+            ]
+          },
+          "comments": {
+            "description": "Count of comments",
+            "type": "number"
+          },
+          "description": {
+            "description": "Article description or excerpt",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "id": {
+            "description": "Article numeric ID",
+            "type": "number"
+          },
+          "published_at": {
+            "description": "Publication timestamp (ISO 8601 format)",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "reactions": {
+            "description": "Count of public reactions",
+            "type": "number"
+          },
+          "reading_time_minutes": {
+            "description": "Estimated reading time in minutes",
+            "type": "number"
+          },
+          "tags": {
+            "description": "List of tags associated with article",
+            "items": {
+              "type": "string"
+            },
+            "type": "array"
+          },
+          "title": {
+            "description": "Article title",
+            "type": "string"
+          },
+          "url": {
+            "description": "Article URL",
+            "type": "string"
+          }
+        },
+        "required": [
+          "id",
+          "title",
+          "description",
+          "url",
+          "published_at",
+          "tags",
+          "reading_time_minutes",
+          "reactions",
+          "comments",
+          "author"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    }
+  },
+  "required": [
+    "articles"
+  ],
+  "type": "object"
+}

Changed1 schema field changedMay 6, 2026

addedInput schema / examples

Added value: +[
+  {
+    "limit": 10,
+    "tag": "javascript"
+  },
+  {
+    "limit": 20,
+    "tag": "python",
+    "top": 7
+  }
+]

First observedApr 14, 2026

TDQS

A4/5.0

Behavior4/5

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

Annotations already declare the read-only, idempotent, non-destructive nature. The description adds useful behavioral context: sorting order (publication date) and the specific fields returned (title, summary, URL, image, source), which goes beyond schema details.

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 concise, front-loaded with the action, and uses only two sentences that convey the purpose and return value without redundancy.

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?

Given the simplicity (one optional parameter, clear output schema, and strong annotations), the description is complete enough. It conveys the core behavior and return details, with no missing critical information for a basic fetch operation.

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. The description does not add additional detail about parameters, so a 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 fetches the latest spaceflight news articles with a specific sorting (by publication date). This distinguishes it from siblings like search_articles or get_blogs.

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?

The description implies use when you want the latest articles but does not explicitly mention alternatives or when-not-to-use scenarios. No guidance is given for choosing between this and search-related siblings.

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

All Spacenews 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.

Get Articles

Input Schema

Output Schema

Schema Changelog

TDQS

Glama MCP Gateway

Resources