Skip to main content
Glama
mcp-singapore
by Hug0x0

singapore_find_nearby_facilities

Read-onlyIdempotent

Find nearby Singapore facilities—HDB carparks with live availability, hawker centres, preschools, parks, and sport facilities—by category, coordinates, and radius.

Instructions

Find nearby HDB carparks with live availability, hawker centres, preschools, park facilities or sport facilities. Reads a bounded full official export (64 MiB max). Only Point geometries with validated WGS84 coordinates are considered; omitted geometries are counted. No arbitrary download URL input.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "category": "<category>",
      "latitude": "<latitude>",
      "longitude": "<longitude>"
    },
    "name": "singapore_find_nearby_facilities"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
offsetNo
categoryYes
latitudeYes
longitudeYes
radius_kmNo
include_propertiesNo

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.5/5.0
Behavior4/5

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

Annotations already cover read-only, idempotent, non-destructive and open-world status, so the bar is lower. The description still adds real behavioral context: a bounded official export of at most 64 MiB, the rule that only Point geometries with validated WGS84 coordinates are considered, and that omitted geometries are counted — all useful for interpreting result completeness.

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?

Three compact sentences with the primary action front-loaded, then the data-scope guarantees, then the negative constraint. No filler and nothing repeated from the schema.

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?

An output schema exists, so return-value explanation is not required, and the export-size and geometry caveats are helpful. However, an agent still cannot infer from the description that proximity is controlled by radius_km with a 2 km default or how pagination behaves — meaningful gaps for a 7-parameter geo query.

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 0%, so the description must carry the parameter semantics, and it only partially does. It maps the category set and implies the coordinate validation for latitude/longitude, but says nothing about radius_km (default 2, max 100), limit/offset pagination behavior, or what include_properties changes in the response.

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?

States a specific verb and resource set: 'Find nearby' plus an explicit enumeration of the five category types (HDB carparks with live availability, hawker centres, preschools, park and sport facilities). This distinguishes it from pure directory lookups like singapore_query_carpark_directory by flagging 'live availability', though it does not name any sibling outright.

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

Usage Guidelines3/5

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

Usage is implied by the category list and by the negative constraint 'No arbitrary download URL input', which implicitly routes URL-based retrieval to singapore_download_dataset. But there is no explicit when-to-use/when-not statement and no guidance on choosing between this and singapore_get_carpark_availability for live data.

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