FeedMyAgent

Get Latest Feed Items

get_latest

Read-only

Get the latest items from the ainews feed (technology, compliance, and security news for AI agents), newest first, optionally filtered by tags, source, or product. Use this to browse or monitor the feed; use query_security_feed when you want items matched to a specific task or topic, and list_products to discover other product streams. Needs no API key.

Input Schema

Name	Required	Description	Default
`tags`	No	Optional tag filters.
`limit`	No	How many items to return; smaller values keep responses short.
`source`	No	Optional source filter.
`product`	No	Optional product stream to read (default ainews).	ainews
`section`	No	Optional: "news" (default) leaves out research papers; "research" returns only papers (arXiv and similar); "all" mixes both.	news

Output Schema

Name	Required	Description	Default
`data`	Yes	Matching feed items.
`source`	Yes	Provenance of the payload.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 22, 2026

addedInput schema / properties / section

Added value: +{
+  "default": "news",
+  "description": "Optional: \"news\" (default) leaves out research papers; \"research\" returns only papers (arXiv and similar); \"all\" mixes both.",
+  "enum": [
+    "news",
+    "research",
+    "all"
+  ],
+  "type": "string"
+}

Changed1 schema field changedOct 15, 2026

changedInput schema / properties / limit / description

Previous value: -"Maximum number of items to return."New value: +"How many items to return; smaller values keep responses short."

Changed1 schema field changedSep 30, 2026

addedInput schema / properties / product

Added value: +{
+  "default": "ainews",
+  "description": "Optional product stream to read (default ainews).",
+  "enum": [
+    "ainews",
+    "events"
+  ],
+  "type": "string"
+}

Changed1 schema field changedSep 22, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "additionalProperties": false,
+  "properties": {
+    "data": {
+      "description": "Matching feed items.",
+      "items": {
+        "additionalProperties": false,
+        "properties": {
+          "id": {
+            "description": "Item id.",
+            "type": "string"
+          },
+          "score": {
+            "description": "Community ranking score.",
+            "type": "number"
+          },
+          "summary": {
+            "description": "Short summary, or null when the item has not been enriched yet.",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "tags": {
+            "description": "Classifier tags.",
+            "items": {
+              "type": "string"
+            },
+            "type": "array"
+          },
+          "title": {
+            "description": "Item title.",
+            "type": "string"
+          },
+          "url": {
+            "description": "Canonical item URL.",
+            "type": "string"
+          }
+        },
+        "required": [
+          "id",
+          "title",
+          "summary",
+          "tags",
+          "score",
+          "url"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "source": {
+      "additionalProperties": false,
+      "description": "Provenance of the payload.",
+      "properties": {
+        "name": {
+          "description": "Feed name.",
+          "type": "string"
+        },
+        "url": {
+          "description": "Feed homepage URL.",
+          "type": "string"
+        }
+      },
+      "required": [
+        "name",
+        "url"
+      ],
+      "type": "object"
+    }
+  },
+  "required": [
+    "data",
+    "source"
+  ],
+  "type": "object"
+}

First observedSep 22, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Annotations already declare readOnly=true, destructive=false, openWorld=true, so safety is covered; the description adds genuinely new context — newest-first ordering and 'Needs no API key' (a real auth requirement disclosure). It does not discuss pagination or result volume beyond the schema's default limit, keeping it short of a 5.

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?

Two sentences, front-loaded with the primary action and scope, followed by routing guidance. No filler or 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?

With a full output schema, complete annotations, and 100% schema coverage, the description only needs to add orientation and routing, which it does. Partial demerit: the prose mentions tags, source, and product filters but omits the equally relevant `section` parameter, creating a small gap between prose and actual behavior.

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 schema already documents all five parameters including the enum semantics for source, product, and section. The description only restates that filtering is optional by tags, source, or product, adding ordering information but nothing about parameter syntax or interaction; baseline 3 applies.

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?

States a specific verb and resource ('Get the latest items from the ainews feed'), names the domain (technology, compliance, security news for AI agents), and specifies ordering ('newest first') plus optional filters. It is unmistakable against siblings like query_security_feed or list_products.

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

Usage Guidelines5/5

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

Explicitly routes usage: 'Use this to browse or monitor the feed; use query_security_feed when you want items matched to a specific task or topic, and list_products to discover other product streams.' Both the use case and the alternatives with their selecting conditions are named.

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

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