Skip to main content
Glama

Inferventis MCP Server

web_news_headlines

Retrieves the latest real-time news headlines and article summaries from BBC News and The Guardian across nine topic categories. Returns structured articles with headline, description, source name, article URL, and publication date — sorted most recent first. No API key required. Use this tool when an agent needs current news about a specific topic, wants to summarise today's headlines, needs to research recent events, monitor a subject area for new developments, or build a news briefing. Do not use this tool to read the full content of a specific article — use web_url_reader instead, passing the article URL returned by this tool. Do not use when news from sources outside BBC News and The Guardian is required.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoMaximum number of articles to return. Integer between 1 and 20. Defaults to 10. Use a lower number for a quick briefing and a higher number for comprehensive coverage.
topicNoNews topic category to retrieve headlines for. Accepted values: 'general' (top stories across all categories), 'technology' (tech industry and digital news), 'business' (markets, economy, and corporate news), 'science' (research, environment, and discoveries), 'health' (medical and public health news), 'politics' (government and political news), 'sport' (sports and athletics), 'ai' (artificial intelligence and machine learning news), 'world' (international and global news). Defaults to 'general' if omitted or unrecognised.
keywordNoOptional search keyword to filter headlines. Only articles whose title or description contains this keyword will be returned. Case-insensitive. Examples: 'OpenAI', 'interest rates', 'climate change'. Omit to return all headlines for the chosen topic.

TDQS

A4.4/5.0
Behavior4/5

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

With no annotations provided, the description carries the full transparency burden. It discloses key behavioral traits: real-time data, source restriction, sorted output, and no API key requirement. It stops short of covering error/rate-limit details but adds valuable context beyond the schema.

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 concise yet comprehensive, opening with the core function, then detailing usage guidance and exclusions. Every sentence contributes to the description without redundancy, achieving strong front-loading.

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?

Even without an output schema, the description explains return fields, sorting order, and source constraints, complementing the rich input schema. It provides sufficient context for an agent to select and invoke the tool, though it omits minor details like empty-result behavior.

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%, with each parameter (limit, topic, keyword) already thoroughly documented. The description adds no additional parameter-specific semantics beyond what the schema provides, so the baseline score of 3 applies.

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 the tool retrieves real-time news headlines and article summaries from BBC News and The Guardian, specifying the verb 'retrieves' and the resource (headlines and summaries). It also lists output fields and sources, distinguishing it from siblings like web_url_reader.

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?

Explicitly provides when-to-use scenarios (summarize headlines, research events, monitor topics) and when-not-to-use, directing users to web_url_reader for full article content and noting the source limitation to BBC and Guardian.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A3.9/5.0
Disambiguation2/5

Multiple tools have overlapping purposes, particularly the five fiat FX tools (currency_convert, currency_convert_lite, currency_convert_open, currency_fx_lite, currency_rates) and the three crypto tools (crypto_fx_rates, crypto_price, crypto_price_lite). Although descriptions attempt to differentiate them by source or detail level, the boundaries are subtle enough that an agent could easily misselect.

Naming Consistency3/5

Tool names use a mix of noun_noun, noun_verb, and adjective_noun patterns. Some include a 'lite' suffix consistently, but others like 'finnhub_stock_quote' and 'stripe_payment_records' have vendor prefixes, while bank tools lack them. Overall, the naming is readable but lacks a single consistent pattern.

Tool Count3/5

At 20 tools, the server covers a broad scope (finance, news, web, timezone) but includes redundancy (e.g., five FX conversion tools, two financial calculators). The count is not excessive for a general utility server, but it feels slightly bloated due to multiple near-identical variants.

Completeness3/5

The tool set covers many common financial and informational needs, but notable gaps exist: no historical stock data, no support for non-Stripe payment processors, and no ability to initiate payments (read-only). The news sources are limited to BBC and Guardian. Some areas are over-covered while others are missing, resulting in moderate completeness.

Resources