Skip to main content
Glama

search_swiss_news

Read-onlyIdempotent

Search current SRF headlines by keyword or phrase to find relevant Swiss news across all categories.

Instructions

Keyword search in current SRF headlines (all categories)

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "query": "<query>"
    },
    "name": "search_swiss_news"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNomax 20
queryYesKeyword or phrase

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv0.9.0
    • addedInput schema / properties / limit / default
      Added value: +5
    • changedInput schema / properties / limit / description
      Previous value: -"Maximum number of results to return (default: 5, max: 20)"New value: +"max 20"
    • changedInput schema / properties / query / description
      Previous value: -"Search keyword or phrase to find in news articles"New value: +"Keyword or phrase"
  2. First observed

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, openWorld and non-destructive. The description adds that coverage is limited to 'current' headlines across all categories, which usefully implies no archive search, but says nothing about result ordering or freshness window beyond that.

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?

One short sentence with the source, operation, and scope front-loaded and no filler. Nothing could be removed without losing information.

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?

For a two-parameter read tool with annotations this is close to adequate, but with no output schema, the agent cannot tell what a result contains (headline only, link, timestamp, category) or how results are ranked.

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%, including the 'max 20' cap on limit and 'Keyword or phrase' for query. The description adds no meaning beyond that, so the baseline of 3 applies.

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?

States a specific verb (keyword search) and resource (current SRF headlines), naming the source and category scope. This distinguishes it from get_swiss_news, which presumably retrieves rather than searches, though the contrast is only implicit.

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 name pair: search here for keywords, use get_swiss_news otherwise. No explicit when-to-use, when-not-to-use, or named alternative is given, so the agent must infer the routing.

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