Skip to main content
Glama
AI Pulse Radar MCP

AI Pulse Radar MCP

fetch_global_news_and_community_pulse

Fetch real-time news and community sentiment across Google News RSS, Reddit, and Hacker News by keywords to monitor trends and public opinion.

Instructions

Fetch real-time news and community sentiment across Google News RSS, Reddit, and Hacker News.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "keywords": "<keywords>"
    },
    "name": "fetch_global_news_and_community_pulse"
  }
}

Input Schema

NameRequiredDescriptionDefault
keywordsYesKeywords to search (e.g., ['AI agents', 'Bitcoin'])
languageNoGoogle News language code (e.g., 'en-US', 'ko')en-US
maxItemsPerSourceNoMax items per platform (default: 10)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/5.0
Behavior2/5

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

With no annotations at all, the description carries the full disclosure burden and does not meet it. It reveals the three external sources and that results are 'real-time' (implying network calls and possible latency or per-source failures), but says nothing about rate limits, auth requirements, partial-failure behavior when one source errors, or how 'community sentiment' is derived.

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?

A single front-loaded sentence with no filler; the action, the outputs, and the sources all land immediately.

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?

For a three-parameter read tool with no output schema and no annotations, the description is nearly adequate: sources and data type are clear. The remaining gap is return-shape information — how sentiment and mixed-source results are presented — which leaves the agent guessing about response structure.

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 three parameters are already documented, and the baseline of 3 applies. The description adds no parameter-level meaning beyond the schema — notably it does not explain that 'language' applies only to Google News or how multiple 'keywords' are combined (OR vs AND across platforms).

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 pairs a specific verb ('Fetch') with two concrete resources ('real-time news and community sentiment') and names the exact upstream sources (Google News RSS, Reddit, Hacker News). It clearly distinguishes itself from a generic search tool by scoping to these sources, though there are no siblings to differentiate against.

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 when-to-use, when-not-to-use, or prerequisite guidance. The mention of 'real-time' implies it is for current-events lookups, but an agent must infer that; nothing states freshness limits, whether it should be preferred over a general web search, or what to do when a source is unavailable.

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

Deploy Server

Other Tools