Skip to main content
Glama
malkreide

news-monitor-mcp

by malkreide

news_geo_search

Read-onlyIdempotent

Search news articles by geographic location and get sentiment scores. Provide a location and optional query to receive relevant, geolocated news.

Instructions

Standortspezifische Nachrichtensuche (Cache-TTL: 30 Min).

Args: params (GeoNewsInput): location, query, language, days_back, number, use_cache, response_format

Returns: str: Geolokalisierte Nachrichtenartikel mit Sentiment.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
paramsYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior4/5

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

Annotations declare readOnlyHint, idempotentHint, and destructiveHint false. The description adds cache TTL of 30 minutes, which is a behavioral detail not present in annotations. No contradictions.

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?

The description is very concise: one line for purpose and cache, then a function signature. No filler. Could be slightly more structured, but front-loads the key purpose.

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

Completeness2/5

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

Given the tool has many siblings and is location-specific, more context is needed on how the location parameter works (e.g., format, supported locations). The output schema exists but is not described. The description leaves gaps for effective use.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% according to context. The description lists parameter names but provides no additional meaning, constraints, or examples beyond the schema. This fails to compensate for the lack of schema descriptions.

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?

The description clearly states it's a location-specific news search, with 'Standortspezifische Nachrichtensuche'. This distinguishes it from sibling tools like news_search and news_top_headlines by specifying the geographic scope.

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?

No explicit guidance on when to use this tool vs alternatives. The description mentions it's location-specific, but does not provide scenarios or exclusions. Sibling tools include other news search tools, but no comparative guidance.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/malkreide/news-monitor-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server