mcp-singapore

singapore_get_rainfall

Read-onlyIdempotent

Retrieve Singapore NEA rainfall measurements in millimeters by area, region, station, or local date; omit the date to get the latest readings.

Instructions

NEA rainfall (mm). Singapore local dates; latest if omitted. Local limits apply to timestamp groups. Consume local offsets before continuing the preserved upstream pagination token.

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

Input Schema

Name	Required	Description
`area`	No
`date`	No	Singapore local time UTC+08:00: YYYY-MM-DD or YYYY-MM-DDTHH:mm:ss
`limit`	No
`offset`	No
`region`	No
`station_id`	No
`pagination_token`	No

Output Schema

Name	Required	Description	Default
`ok`	Yes
`data`	No
`error`	No
`status`	No
`sources`	Yes
`metadata`	No
`provider`	No
`warnings`	No
`served_at`	Yes
`error_code`	No
`source_url`	No
`dataset_url`	No
`catalog_metadata`	No
`catalog_snapshot_at`	No
`retry_after_seconds`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.2.0Oct 23, 2026

TDQS

C2.8/5.0

Behavior3/5

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

Annotations already declare readOnly/idempotent/non-destructive, so safety is covered. The description adds useful context (mm unit, latest-when-omitted default) plus a cryptic pagination caveat ('consume local offsets before continuing the preserved upstream pagination token') and 'local limits apply to timestamp groups' that hint at behavior without really clarifying it.

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

Conciseness3/5

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

It is short and front-loads the resource, but the final sentence is jargon-laden and hard to parse, spending words without conveying a clear instruction.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With 7 parameters, 0 required, and near-zero schema coverage, the description should explain the geographic filters and pagination contract. An output schema exists so return format need not be covered, but the filter semantics and the pagination-token/offset relationship are left ambiguous.

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

Parameters2/5

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

Schema description coverage is only 14% — only 'date' is documented — so the description carries the burden and largely fails to. area, region, and station_id are never explained (mutual exclusivity? granularity?), and limit/offset/pagination_token interactions are only alluded to in opaque terms.

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 identifies the specific data resource (NEA rainfall measured in mm), which cleanly separates it from the weather siblings such as singapore_get_air_temperature or singapore_get_wind_speed. The verb is only implicit through the tool name, but the resource and unit are unambiguous.

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

Usage Guidelines2/5

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

The only usage-adjacent statement is 'latest if omitted', which describes a default rather than when to choose this tool. There is no comparison to sibling weather endpoints or any statement about prerequisites or when not to use it.

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

Deploy Server