Skip to main content
Glama

Singapore Digital Twin · Sea level rise and live data

places_underwater

Read-only

Named public places (hawker centres, schools, places of worship) reached by the sea at a rise, optionally of one kind or in one planning area.

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

Input Schema

NameRequiredDescriptionDefault
areaNoLimit to one planning area.
kindNo
langNoLanguage of the answer: "en" (default) or "fr".
yearNoA year, 2025-2150 (with scenario), instead of rise_m.
limitNoMost names to list (default 20).
rise_mNoSea-level rise in metres above today's mean high water (0-9).
scenarioNomoderate = SSP2-4.5, high = SSP5-8.5 (very high emissions), upper = SSP5-8.5 upper range (planning). Default high.
storm_surgeNoAdd an extreme storm surge and high tide (+1.3 m) on top.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / scenario / description
      Previous value: -"moderate = SSP2-4.5, high = SSP5-8.5, upper = SSP5-8.5 high end (planning). Default high."New value: +"moderate = SSP2-4.5, high = SSP5-8.5 (very high emissions), upper = SSP5-8.5 upper range (planning). Default high."
  2. First observed

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety and scope are covered. The description adds value by defining the result set as named public places in three specific categories, but it says nothing about ordering, pagination behavior of limit, or whether a rise with no affected places returns empty versus omitted.

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?

A single sentence with the core subject front-loaded and no filler. The phrasing 'reached by the sea at a rise' is slightly awkward but earns its space.

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

Completeness3/5

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

For an 8-parameter tool with no output schema, the definition should say more about the shape of results (names only, or names plus area/rise) and about the mutual exclusivity of year and rise_m. The strong schema coverage offsets some of this, but the description leaves gaps an agent would want filled.

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 coverage is 88%, so the schema already documents nearly every parameter; the description only echoes kind and area. It adds no meaning for the year-vs-rise_m tradeoff, storm_surge, scenario, or limit, so baseline 3 applies.

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 resource — named public places (hawker centres, schools, places of worship) that are inundated at a given sea-level rise — which is concrete enough for an agent to grasp the output. The verb is implicit ('reached by the sea') rather than stated, and it draws no distinction from siblings like flood_impact or check_address.

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?

There is no when-to-use or when-not-to-use guidance, and no sibling is named as an alternative. The phrase 'optionally of one kind or in one planning area' describes filtering options rather than the conditions that should select this tool over another.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources