Skip to main content
Glama

get_swiss_news

Read-onlyIdempotent

Fetch current SRF news headlines by category (Switzerland, international, economy) with a configurable limit. Retrieve Swiss news updates without API keys.

Instructions

Latest SRF news headlines

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
limitNomax 50
categoryNoswitzerland

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changedv0.9.0
    • addedInput schema / properties / category / default
      Added value: +"switzerland"
    • removedInput schema / properties / category / description
      Removed value: -"News category. \"switzerland\" = domestic Swiss news (default), \"international\" = world news, \"economy\" = business & economy."
    • addedInput schema / properties / limit / default
      Added value: +10
    • changedInput schema / properties / limit / description
      Previous value: -"Number of articles to return (default: 10, max: 50)"New value: +"max 50"
  2. First observed

TDQS

C2.4/5.0
Behavior2/5

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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint and destructiveHint=false, so the safety profile is covered. The description adds nothing beyond that: it does not define how far back "latest" reaches, whether results are cached or live, or what the headline records contain.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Four words with zero padding and a front-loaded subject, but the brevity is under-specification rather than economy. Nothing in the phrase earns the omission of freshness window and sibling routing.

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?

For a two-parameter tool with no output schema, the description should at minimum define the recency window and clarify the relationship to search_swiss_news. Neither is present, leaving an agent unable to call it confidently beyond defaults.

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%: limit carries "max 50" while category is a bare enum with a default and no explanation. The description mentions neither parameter, so it fails to compensate for the gap and adds no meaning about what categories select or how limit affects ordering.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

"Latest SRF news headlines" identifies the resource (SRF news) and scope (latest), so an agent knows roughly what comes back. But there is no verb and no differentiation from the sibling tool search_swiss_news, so the agent cannot tell which of the two to pick.

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 guidance at all, and crucially no statement of how this differs from search_swiss_news. The agent must guess based on names alone.

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