Skip to main content
Glama

Infectious disease cases & incidence

get_disease_surveillance
Read-only

Retrieve Swiss FOPH disease surveillance data by topic and region, including reported cases or detections per week, month, or year, plus incidence and trends.

Instructions

Latest surveillance data for one FOPH topic and region: reported cases (or GP consultations / detections / wastewater load) per week, month or year, with incidence per 100'000 and trend where published. region: 'CHFL' (Switzerland + Liechtenstein, default for mandatory reporting), 'CH', a canton code ('ZH'), or a wastewater plant (e.g. 'basel'). breakdown: 'agegroup', 'sex', 'pathogen' or 'subtype' (variants) to split the totals. Recent periods are provisional. Example: {topic: 'influenza', region: 'ZH', last_periods: 8}.

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": {
      "topic": "<topic>"
    },
    "name": "get_disease_surveillance"
  }
}

Input Schema

NameRequiredDescriptionDefault
fromNoReturn all periods from this one on instead, e.g. '2025-W40', '2024-M01', '2025-10-01'
topicYesTopic id from list_disease_surveillance_topics, e.g. 'influenza', 'covid19', 'tbe', 'respiratory_viruses_wastewater'
regionNoCHFL, CH, FL, a canton code (ZH, BE, …) or a wastewater plant nameCHFL
filtersNoPin other dimensions, e.g. {pathogen: 'influenza'}
breakdownNoSplit totals by this dimension
last_periodsNoNumber of most recent periods (weeks/months/years) to return
value_categoryNoMeasure, e.g. 'cases', 'consultations', 'detections', or a virus for wastewater ('influenza_a', 'sars-cov-2'); defaults to the main one

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.3

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, so safety is covered; the description adds genuinely new context — that values are FOPH surveillance figures and that 'recent periods are provisional'. That caveat is decision-relevant for an agent reporting numbers. Return shape is only loosely sketched, but no output schema exists so some burden remains.

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

Conciseness4/5

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

Front-loads what is returned, then parameter semantics, then the provisional-data caveat, closing with a compact call example. Dense but every clause carries information; only the parenthetical measure list is slightly baggy.

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 7-parameter tool with a nested filters object and no output schema, the description covers the high-traffic parameters (topic, region, breakdown, last_periods) and dataset caveats well. It leaves 'from' and the free-form 'pathogen'/'value_category' pinning largely to the schema, which is acceptable at 100% coverage but is a small remaining gap.

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

Parameters4/5

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

Schema coverage is 100%, so the baseline is 3, but the description earns a bump by explaining the *meaning* behind enumerated values: why 'CHFL' is the default, what breakdown dimensions represent ('variants' for subtype), and a worked example combining topic, region, and last_periods. It adds no detail on 'from' or the nested 'filters' object beyond what the schema states.

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?

Names a specific verb and resource ('latest surveillance data for one FOPH topic and region') and immediately enumerates the measures returned (cases, GP consultations, detections, wastewater load) with their units (per week/month/year, incidence per 100'000, trend). This is far more specific than the title and lets an agent distinguish it from the topic-listing sibling without opening the schema.

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?

Gives concrete selection guidance for the key dimensions: region accepts 'CHFL' as the default for mandatory reporting, a canton code, or a wastewater plant; breakdown names the four splits. It does not explicitly state when to prefer this over a sibling or that the topic id must first come from list_disease_surveillance_topics (that routing hint lives only in the schema), so no exclusion guidance is present.

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