Skip to main content
Glama

FOPH disease surveillance topics

list_disease_surveillance_topics
Read-only

Lists FOPH infectious-disease surveillance topics with IDs, disease, system, and time resolution so you can select the right ID for get_disease_surveillance.

Instructions

Topics available from the FOPH infectious-disease dashboard (id, disease, surveillance system, time resolution). Use the id with get_disease_surveillance.

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": "list_disease_surveillance_topics"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.3

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, and the description adds real value beyond them by listing exactly which attributes each topic carries. It does not cover pagination, whether the topic list is static, or auth needs, but for a read-only enumeration tool those are minor.

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?

Two sentences, zero waste: the first defines the resource and its returned fields, the second gives the follow-up action. The resource definition is front-loaded before the workflow hint.

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 no output schema, the description compensates by naming the four fields returned, which is what an agent needs to decide whether to call this or the fetch tool. Only minor gaps remain, such as whether the list is exhaustive or paginated.

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?

The tool takes no parameters, so there is nothing for the description to disambiguate beyond what the empty schema already shows. Baseline 4 applies; the description correctly avoids inventing filtering options that do not exist.

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?

States a specific resource (topics from the FOPH infectious-disease dashboard) and enumerates the returned fields (id, disease, surveillance system, time resolution), which immediately separates it from the data-fetching sibling. An agent knows this is a discovery/enumeration tool, not a data query tool.

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?

Explicitly directs the agent to use the returned id with get_disease_surveillance, which establishes the discover-then-fetch workflow. It stops short of saying 'call this first' or naming any case where this tool is unnecessary, so it is clear context rather than full when/when-not guidance.

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