Skip to main content
Glama

FeedMyAgent

by io.github.makash
OverviewDiscussionsAdmin

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. Read-only: returns public feed data and needs no API key.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
tagsNoOptional tag filters.
limitNoMaximum number of items to return.
sourceNoOptional source filter.
productNoOptional product stream to read (default ainews).ainews

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
dataYesMatching feed items.
sourceYesProvenance of the payload.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / product
      Added value: +{
+  "default": "ainews",
+  "description": "Optional product stream to read (default ainews).",
+  "enum": [
+    "ainews",
+    "events"
+  ],
+  "type": "string"
+}
  2. Changed1 schema field changed
    • 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"
+}
  3. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, openWorldHint=true, and destructiveHint=false, so the safety profile is covered. The description adds genuinely new context the annotations do not carry: public feed data, no API key required, and newest-first ordering. It does not cover rate limits or response shape, so it is not a full 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, zero waste, with the core purpose front-loaded before the routing guidance to siblings. Every clause earns its place by adding scope, ordering, or alternative selection.

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?

An output schema exists, so return values need not be explained. Combined with annotations covering safety and the description covering scope, ordering, and auth needs, an agent has everything required to invoke this correctly.

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 baseline is 3. The description restates the filter dimensions (tags, source, product) already documented in the schema and adds no syntax or format detail, e.g. how multiple tags combine or how source/product interact with the default product stream.

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 (get) and resource (latest items from the ainews feed), plus scope details (technology, compliance, security news for AI agents) and ordering (newest first). It explicitly names the siblings it is not (query_security_feed, list_products), so an agent can route without opening schemas.

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?

Gives explicit use conditions: browse or monitor the feed here, use query_security_feed for task/topic-matched items, and list_products to discover product streams. Both when-to-use and the alternative selection criteria are stated.

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

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