Skip to main content
Glama

MeteoSwiss MCP Server

by io.github.eins78
OverviewDiscussionsAdmin

search

Search MeteoSwiss website content in multiple languages (DE, FR, IT, EN). Returns relevant pages with URLs that can be passed to the fetch tool. Always returns up to 10 results per page — the upstream API has a fixed page size that cannot be changed. Note: pagination may return duplicate results across pages (upstream API limitation).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pageNoPage number for pagination (1-based). The upstream API always returns 10 results per page; page size is not configurable.
sortNoSort order for results. Note: date-asc severely degrades relevance — results are dominated by page age rather than query match.relevance
queryYesThe search query string
languageNoThe language for search resultsde
contentTypeNoFilter by content type. Defaults to "content" to exclude application pages. Use "publication" for official reports.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
pageYesCurrent page number (1-based)
resultsYesResult items for this page
pageSizeYesNumber of items in `results` for this page — at most 10 (the upstream API pages by a fixed 10), fewer on the last page
totalResultsYesTotal number of matches across all pages

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changed
    • changedInput schema / properties / page / description
      Previous value: -"Page number for pagination (1-based)"New value: +"Page number for pagination (1-based). The upstream API always returns 10 results per page; page size is not configurable."
    • changedInput schema / properties / page / maximum
      Previous value: -9007199254740991New value: +1000
    • removedInput schema / properties / pageSize
      Removed value: -{
-  "default": 12,
-  "description": "Number of results per page (max 100)",
-  "exclusiveMinimum": 0,
-  "maximum": 100,
-  "type": "integer"
-}
    • addedInput schema / properties / query / maxLength
      Added value: +200
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": false,
+  "properties": {
+    "page": {
+      "description": "Current page number (1-based)",
+      "type": "number"
+    },
+    "pageSize": {
+      "description": "Number of items in `results` for this page — at most 10 (the upstream API pages by a fixed 10), fewer on the last page",
+      "type": "number"
+    },
+    "results": {
+      "description": "Result items for this page",
+      "items": {
+        "additionalProperties": false,
+        "properties": {
+          "contentType": {
+            "description": "Content type of the result",
+            "type": "string"
+          },
+          "description": {
+            "description": "Short description of the page",
+            "type": "string"
+          },
+          "id": {
+            "description": "Result identifier — the page URL (pass to the fetch tool)",
+            "type": "string"
+          },
+          "lastModified": {
+            "description": "Last modification date",
+            "type": "string"
+          },
+          "lead": {
+            "description": "Lead/teaser text",
+            "type": "string"
+          },
+          "path": {
+            "description": "Site path of the page",
+            "type": "string"
+          },
+          "publicationDate": {
+            "description": "Publication date",
+            "type": "string"
+          },
+          "title": {
+            "description": "Page title",
+            "type": "string"
+          },
+          "url": {
+            "description": "Full page URL",
+            "type": "string"
+          }
+        },
+        "required": [
+          "id",
+          "title",
+          "url"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "totalResults": {
+      "description": "Total number of matches across all pages",
+      "type": "number"
+    }
+  },
+  "required": [
+    "totalResults",
+    "page",
+    "pageSize",
+    "results"
+  ],
+  "type": "object"
+}
  2. Changed1 schema field changed
    • changedInput schema / properties / sort / description
      Previous value: -"Sort order for results"New value: +"Sort order for results. Note: date-asc severely degrades relevance — results are dominated by page age rather than query match."
  3. First observed

TDQS

A4.2/5.0
Behavior4/5

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

No annotations are provided, so the description carries the full burden. It discloses the fixed 10-result page size and the upstream duplication limitation, which are critical behavioral traits. It does not cover every edge case, but for a search tool these are the key operational constraints.

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 sentences, front-loaded with the purpose, followed by behavioral notes and a limitation. Every sentence earns its place, with no redundant content.

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?

With an output schema and rich parameter descriptions, the description covers the essential operational quirks (fixed page size, duplicates) and the workflow (pass URLs to fetch). It could mention sort behavior, but that is already in the schema, so the description is sufficiently complete.

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?

All five parameters are fully documented in the schema (100% coverage), so the description adds only marginal value beyond the schema. It mentions language support and the fixed page size, but these are already reflected in parameter descriptions, so baseline 3 is appropriate.

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 'Search MeteoSwiss website content' with specific verb and resource, and notes multi-language support. It distinguishes itself from sibling tools like meteoswissCurrentWeather and meteoswissClimateData, which focus on data rather than website content.

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

Usage Guidelines4/5

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

The description explicitly mentions that returned URLs can be passed to the fetch tool, establishing a clear usage workflow. It does not explicitly name alternatives or exclusions, but the tool's scope is evident from sibling names, so guidance is clear despite lacking explicit 'when not to use' statements.

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

All MeteoSwiss MCP Server toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources