Skip to main content
Glama
europe-tech-news-mcp

europe-tech-news-mcp

by MAVRICK-1

get_europe_tech_news

Retrieve ranked European technology news from public feeds and filter by region, topic, and time window for monitoring, research, or briefings.

Instructions

Top recent tech stories from European outlets.

region: europe, eu, uk, ireland, germany/dach, france, benelux/netherlands, nordics/scandinavia, spain/iberia. topic: ai, funding, regulation, security, cloud, opensource, sovereignty, projects, bugs/outages, opportunities/tenders, all/tech, semiconductors, fintech, climate, startups (or any free keyword). days: lookback window, 1-60 (default 7). limit: max stories, 1-50 (default 10).

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_europe_tech_news"
  }
}

Input Schema

NameRequiredDescriptionDefault
daysNo
limitNo
topicNo
regionNoeurope

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full behavioral burden. It discloses defaults and ranges for days and limit, but says nothing about ranking logic, return format, source coverage, authentication, or rate limits.

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?

The description is front-loaded with the purpose and then compactly documents the parameter options. Every line contributes directly to invoking the tool, with no unnecessary prose.

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?

The purpose and all parameters are well covered, but with no output schema and no annotations the description should ideally explain the return shape or ranking behavior. It also omits sibling differentiation and source-selection context.

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

Parameters5/5

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

Schema description coverage is 0%, and the description fully compensates by defining all four parameters. It lists accepted region values, accepted topic values plus free keywords, and gives ranges and defaults for days and limit.

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 states a specific resource and scope: top recent tech stories from European outlets. It is clear enough to identify the tool, but it does not explicitly distinguish itself from sibling tools like get_top_eu_tech_news or search_europe_tech_news.

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?

The description lists acceptable region and topic values but gives no guidance on when to use this tool versus search_europe_tech_news or get_top_eu_tech_news. There are no exclusions or alternative-routing instructions.

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