FeedMyAgent

Query Security Feed

query_security_feed

Read-only

Search the ainews feed for items relevant to what your agent is about to do — technology, compliance, and security news for AI agents — ranked by relevance to your natural-language query. Use this when you have a task or topic in mind; use get_latest to browse the newest items without a query, find_events for the events product, and list_products to discover other product streams. Needs no API key.

Input Schema

Name	Required	Description	Default
`tags`	No	Optional tags an item must all carry (AND), lowercase and hyphenated, e.g. ["mcp", "prompt-injection"] or ["advisory"]. Call get_latest without tags first if you don't know the vocabulary.
`limit`	No	How many items to return; smaller values keep responses short.
`query`	Yes	What your agent is doing or researching, in plain language; matched against item titles, summaries and tags. Example: "adding an MCP server to our coding agent" or "EU AI Act obligations for chatbots".
`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"
+}

Changed3 schema fields 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."

changedInput schema / properties / query / description

Previous value: -"Natural language description of what the agent is doing."New value: +"What your agent is doing or researching, in plain language; matched against item titles, summaries and tags. Example: \"adding an MCP server to our coding agent\" or \"EU AI Act obligations for chatbots\"."

changedInput schema / properties / tags / description

Previous value: -"Optional tag filters applied to feed search."New value: +"Optional tags an item must all carry (AND), lowercase and hyphenated, e.g. [\"mcp\", \"prompt-injection\"] or [\"advisory\"]. Call get_latest without tags first if you don't know the vocabulary."

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 readOnlyHint, openWorldHint and destructiveHint=false, so the description is not burdened with safety disclosure. It adds useful context beyond the annotations: relevance ranking behavior and "Needs no API key," which removes an auth pre-check the agent would otherwise have to make. Return shape is covered by the output schema, so no credit is lost there.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with the core action and ranking behavior, and the sibling routing sentence carries real routing value. Slightly run-on and denser than necessary, but every clause earns its place.

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?

With annotations, a full output schema, and 100% parameter coverage, the description supplies exactly the missing layer: when to reach for this tool versus its siblings and that no API key is needed. Nothing an agent needs in order to call it correctly is absent.

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 all five parameters are already documented, including the query examples and tag vocabulary guidance. The description reinforces the semantic intent of query but adds no syntax, format, or interaction detail beyond the schema; 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 ("Search the ainews feed") plus the ranking mechanism (relevance to a natural-language query) and the content domain (technology, compliance, security news for AI agents). An agent can distinguish it from get_latest and find_events without opening either schema.

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 gives the selecting condition ("when you have a task or topic in mind") and names three alternatives with their respective conditions: get_latest for browsing without a query, find_events for the events product, list_products for other streams. Nothing is left to inference.

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.