Gemral Edge

Federal Policy & Executive Action Feed

get_policy_intelligence_feed

Stream of executive orders, trade policy actions, and regulatory mandates categorized across 6 policy pillars (Tariffs, Energy Deregulation, Defense, Crypto Strategic Reserve, Antitrust, MAHA Healthcare).

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_policy_intelligence_feed"
  }
}

Input Schema

Name	Required	Description	Default
`limit`	No
`policy_pillar`	No	Policy pillar filter

Output Schema

Name	Required	Description
`notice`	No	Free-tier upgrade notice; only when results are masked/delayed.
`results`	Yes	Tool result payload (read-only evidence). Shape varies by tool; scoring weights are never exposed.
`history_limit`	No	Present when the license limits history depth: earliest_allowed date, history_days and how many older items were removed.
`deprecated_fields`	No	Present only while a renamed key is still returned next to its replacement: field (old key), replacement (new key, same value), removal (ISO date after which the old key is gone).

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 26, 2026

addedOutput schema / properties / deprecated_fields

Added value: +{
+  "description": "Present only while a renamed key is still returned next to its replacement: field (old key), replacement (new key, same value), removal (ISO date after which the old key is gone).",
+  "items": {
+    "additionalProperties": true,
+    "type": "object"
+  },
+  "type": "array"
+}

First observedOct 23, 2026

TDQS

C2.9/5.0

Behavior2/5

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

Annotations declare readOnlyHint=false, openWorldHint=false, destructiveHint=false, yet the description describes a passive content stream and never explains ordering, recency window, or whether the call has any effect. It also adds no context on rate limits or freshness, so behavior beyond the annotations is unaddressed.

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?

One tight sentence with no filler, and the pillar taxonomy is front-loaded. It is slightly under-specified rather than over-long, so brevity costs it little.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With an output schema and annotations present, the description need not cover return values or safety. However, it omits any recency/ordering semantics and any routing versus the many sibling policy and catalyst tools, which an agent needs for a two-parameter feed.

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 coverage is 50%: policy_pillar has an enum and a short description, while limit has constraints but no description. The description's 'categorized across 6 policy pillars' reinforces what the filter dimension means but does not explain the limit's purpose or the ordering of returned items.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names a specific resource and enumerates the six policy pillars it covers, so an agent knows exactly what data comes back. It stops short of a verb (it is a noun phrase, 'Stream of...') and gives no explicit differentiation from siblings like get_policy_affected_companies or get_upcoming_catalysts.

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

Usage Guidelines2/5

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

There is no statement of when to use this feed, when not to, or which sibling to pick for a related question. The policy pillar taxonomy implies it is for policy-topic queries, but the agent must infer that entirely.

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

All Gemral Edge 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.