Skip to main content
Glama

Spacenews

by io.github.pipeworx-io
OverviewDiscussionsAdmin

Get Blogs

get_blogs
Read-onlyIdempotent

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

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoNumber of blog posts to return (default 10, max 100)

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
blogsYes
totalYesTotal number of blog posts available
returnedYesNumber of blog posts returned in this response

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "properties": {
+    "blogs": {
+      "items": {
+        "properties": {
+          "id": {
+            "description": "Blog post ID",
+            "type": "number"
+          },
+          "image_url": {
+            "description": "Blog post image URL",
+            "type": "string"
+          },
+          "published_at": {
+            "description": "Publication date (ISO 8601)",
+            "type": "string"
+          },
+          "source": {
+            "description": "Blog source",
+            "type": "string"
+          },
+          "summary": {
+            "description": "Blog post summary",
+            "type": "string"
+          },
+          "title": {
+            "description": "Blog post title",
+            "type": "string"
+          },
+          "url": {
+            "description": "Blog post URL",
+            "type": "string"
+          }
+        },
+        "required": [
+          "id",
+          "title",
+          "summary",
+          "url",
+          "image_url",
+          "source",
+          "published_at"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "returned": {
+      "description": "Number of blog posts returned in this response",
+      "type": "number"
+    },
+    "total": {
+      "description": "Total number of blog posts available",
+      "type": "number"
+    }
+  },
+  "required": [
+    "total",
+    "returned",
+    "blogs"
+  ],
+  "type": "object"
+}
  2. Changed1 schema field changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "limit": 10
+  },
+  {
+    "limit": 20
+  }
+]
  3. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already cover safety (readOnly, idempotent, non-destructive), and the description adds useful behavioral context: sorting by publication date and the exact return fields (title, summary, URL, image, source). This goes beyond the annotations without contradicting them.

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 concise sentences, front-loaded with the action and resource, and every word adds value. It avoids redundancy and is appropriately sized for the tool's simplicity.

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 tool's simplicity (one optional parameter, strong annotations, and an output schema), the description is complete. It covers all essential aspects: what is fetched, sorting, and return fields, without missing critical information.

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 fully describes the single optional 'limit' parameter with default and max values. The description does not add additional parameter-level semantics, relying on the schema's 100% coverage, 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 specific action ('Fetch') and resource ('latest spaceflight blog posts'), and distinguishes it from siblings like get_articles by specifying the 'spaceflight' domain. It also mentions the sorting criterion, making the purpose 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 when to use this tool: when the latest spaceflight blog posts are needed. It provides clear context but does not explicitly mention alternatives or exclusions, such as when to use search_articles instead for more specific queries.

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

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