Skip to main content
Glama

Latest Swiss news headlines

get_swiss_news
Read-only

Fetch Swiss news headlines from SRF with links and publication times, optionally filtered by keyword. Returns titles, links, and dates only—no summaries or article text.

Instructions

Latest Swiss news headlines from SRF with links and publication times. Optionally filter by keyword. Returns titles, links and dates only; no summaries or article text (these stay at the source, per licence).

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

Input Schema

NameRequiredDescriptionDefault
limitNo
keywordNoFilter headlines by keyword (matched against the headline)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.3

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already mark the tool as read-only and open-world, but the description adds useful behavior beyond that: results are limited to titles, links, and dates, and summaries/article text are deliberately excluded for licensing reasons.

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 three short sentences with no wasted wording. Purpose and source are front-loaded, followed by filtering behavior and the important output limitation.

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 simple two-parameter news retrieval tool with no output schema, the description covers source, return fields, and licensing limits well. The main missing piece is the semantics of the limit parameter.

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

Parameters2/5

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

Schema coverage is only 50%, and the description only restates optional keyword filtering without adding meaning. It never explains the limit parameter, including that it controls the number of headlines, despite the schema defining it with default and maximum values.

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 states a specific resource and source: latest Swiss news headlines from SRF, with links and publication times. It is clearly distinguishable from sibling tools like air quality, arrivals, or municipality facts.

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

Usage Guidelines3/5

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

Usage is implied by the purpose, and the description notes optional keyword filtering plus the limitation that article text is not included. However, it gives no explicit when-to-use guidance, prerequisites, or alternatives.

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