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

Input Schema

TableJSON Schema

Name	Required	Description	Default
`tags`	No	Optional tag filters applied to feed search.
`limit`	No	Maximum number of items to return.
`query`	Yes	Natural language description of what the agent is doing.
`product`	No	Optional product stream to read (default ainews).	ainews

Output Schema

TableJSON 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 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.5/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=true, so the safety profile is covered. The description still adds value by disclosing that it returns public feed data and requires no API key, plus that results are relevance-ranked. It does not describe pagination or result volume beyond the limit param, 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 core action and scope, then the routing guidance, then a compact safety line. Every clause carries information; nothing is padded or repeated.

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-value explanation is unnecessary. For a read-only search tool with full schema coverage and clear sibling routing, nothing an agent needs to call it correctly is missing.

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 four parameters (query, tags, limit, product) are already documented in the schema. The description adds only that the query is natural-language task description and that the feed is ainews, without new syntax or format guidance. Baseline 3 applies when the schema does the heavy lifting.

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 for items') plus the ranking behavior and query type. It explicitly distinguishes itself from sibling tools get_latest, find_events, and list_products by name, so an agent can route correctly 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 an explicit when-to-use rule ('when you have a task or topic in mind') and names each alternative with its selecting condition: get_latest for browsing without a query, find_events for the events product, list_products for discovering other streams. This is textbook alternative routing.

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.