Skip to main content
Glama
Hug0x0
by Hug0x0

singapore_query_hdb_population

Read-onlyIdempotent

Query HDB resident population by geographical distribution using exact filters, text search, sorting, field selection, and pagination.

Instructions

Query HDB Resident Population by Geographical Distribution (Housing & Development Board). Topic: population. Inspect dataset d_0a6c6d71f6fa14e2d27e406f1d018439 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

A4.1/5.0
Behavior4/5

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

Annotations already establish read-only, idempotent, open-world, non-destructive behavior. The description adds useful context by noting the bundled catalog coverage and advising metadata retrieval for current coverage, though it does not discuss rate limits 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.

Conciseness4/5

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

The description is front-loaded with the resource and topic, then follows with the inspection prerequisite and supported operations. It is efficient overall, with only minor redundancy in the coverage note.

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 rich annotations, the description does not need to explain return values in detail. It provides the dataset ID and coverage caveat, though it could more explicitly route agents away from the generic query_dataset sibling.

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 50%, so the description must compensate. It names exact filters, column text search, fields, sort, and pagination, which maps to the six parameters, but it does not explain nested object syntax, sort format details, or limit/offset behavior beyond the schema.

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 states a specific verb and resource: query HDB Resident Population by Geographical Distribution. It clearly distinguishes this dataset from sibling HDB query tools such as resale, rentals, and median rent by naming the population topic and dataset ID.

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 gives an explicit prerequisite: inspect dataset d_0a6c6d71f6fa14e2d27e406f1d018439 first for filter fields. It also lists supported operations, but it does not explicitly say when to use this tool versus the generic singapore_query_dataset or other alternatives.

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