Skip to main content
Glama
Hug0x0
by Hug0x0

singapore_query_infectious_diseases

Read-onlyIdempotent

Query Singapore Ministry of Health weekly infectious disease bulletin cases with exact filters, column text search, sorting, and pagination; inspect dataset fields first to build accurate filters.

Instructions

Query Weekly Infectious Disease Bulletin Cases (Ministry of Health). Topic: health. Inspect dataset d_ca168b2cb763640d72c4600a68f9909e first for filter fields. Supports exact filters, column text search, fields, sort and pagination. Returns source coverage from the bundled catalog; fetch metadata for current coverage.

Input Schema

NameRequiredDescriptionDefault
qNoSearch text by column, e.g. {"school_name":"RAFFLES"}
sortNoe.g. month desc, resale_price desc; inspect fields first
limitNo
fieldsNo
offsetNo
filtersNoExact equality by field name, e.g. {"town":"ANG MO KIO"}

Output Schema

NameRequiredDescriptionDefault
okYes
dataNo
errorNo
statusNo
sourcesYes
metadataNo
providerNo
warningsNo
served_atYes
error_codeNo
source_urlNo
dataset_urlNo
catalog_metadataNo
catalog_snapshot_atNo
retry_after_secondsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A3.9/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 behavior. The description adds useful context about inspecting the dataset and source coverage from the bundled catalog, but does not elaborate on limits, latency, or authentication.

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 front-loaded, compact, and free of filler. Each sentence contributes either scope, prerequisite, capability summary, or coverage caveat.

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?

Given the output schema and annotations, the description does not need to explain return values or safety. It covers the main query modes and prerequisites, though it could more explicitly route users away from the generic query tool.

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?

With 50% schema description coverage, the description compensates by distinguishing exact filters from column text search and mentioning fields, sort, and pagination. This adds meaningful semantic guidance beyond the schema, especially for the nested q and filters parameters.

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?

The description names a specific verb and resource: query Weekly Infectious Disease Bulletin Cases from the Ministry of Health. It clearly identifies the dataset and topic, though it does not explicitly distinguish this from the generic singapore_query_dataset sibling.

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?

It provides a concrete prerequisite to inspect the dataset first for filter fields and summarizes supported query capabilities. It does not explicitly state when to use this tool instead of the generic query_dataset tool, but the domain-specific context makes the intended usage clear.

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