Skip to main content
Glama

Singapore Buying Desk (Connective Labs)

by com.connective-labs
OverviewDiscussionsAdmin

Look up a Singapore address, postal code or building

resolve_sg_address
Read-onlyIdempotent

Use when the user gives or asks about a Singapore postal code, block and street, unit number, or building or place name: what building or postal code it is, whether it is an HDB block, a condominium or a commercial building, the nearest MRT/LRT station and roughly how long the walk is, which postal district or HDB town it is in, or what a courier or delivery needs to know (guardhouse, loading bay). Returns the normalized address with block, street, postal code and parsed unit (floor and unit number), latitude and longitude, postal district (plus HDB town for HDB blocks), the 2 nearest MRT/LRT stations with straight-line distance and an approximate walking time, the building type and a one-line delivery note ('unknown' when the type cannot be told). Gives up to 3 candidates when the input is ambiguous and warns when the block, street or floor does not match. Singapore only. Data: OneMap search (Singapore Land Authority), LTA station exits and HDB property data from data.gov.sg. Read-only.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
queryYesOne Singapore location as the user wrote it: a 6-digit postal code, an address with block, street and optional #floor-unit, or a building or place name, e.g. '570151', 'Blk 123 Ang Mo Kio Ave 6 #04-56', 'Suntec Tower 3', 'ION Orchard'. Abbreviations such as Blk, Ave, St, Lor are fine.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / query / description
      Previous value: -"A 6-digit postal code, an address with block, street and optional unit, or a building or place name, e.g. '570151', 'Blk 123 Ang Mo Kio Ave 6 #04-56', 'ION Orchard'."New value: +"One Singapore location as the user wrote it: a 6-digit postal code, an address with block, street and optional #floor-unit, or a building or place name, e.g. '570151', 'Blk 123 Ang Mo Kio Ave 6 #04-56', 'Suntec Tower 3', 'ION Orchard'. Abbreviations such as Blk, Ave, St, Lor are fine."
  2. Added

TDQS

A4.4/5.0
Behavior5/5

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

Annotations already declare read-only, idempotent and open-world, and the description adds substantial behavior beyond them: up to 3 candidates on ambiguous input, explicit mismatch warnings for block/street/floor, 'unknown' fallback for the delivery note, and named upstream data sources (OneMap/SLA, LTA, HDB). This is unusually thorough for a lookup tool.

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?

Front-loaded with the trigger condition, then a dense but justified enumeration of return fields. The long return list is warranted because there is no output schema, though the prose runs as one block and could be broken into shorter sentences.

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

Completeness5/5

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

With no output schema, the description takes on the burden of describing the response (normalized address, coordinates, district/HDB town, two nearest stations with distance and walk time, building type, delivery note) and does so completely, including the ambiguity and mismatch behaviors an agent must handle.

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?

There is a single parameter and schema description coverage is 100%, so the schema already carries accepted forms and examples. The description restates the same input shapes ('as the user wrote it', abbreviations) without adding syntax or constraints the schema lacks, so the baseline of 3 applies.

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?

States a specific verb+resource (resolve/look up a Singapore address, postal code or building) and pins the scope with 'Singapore only'. The sibling list contains no overlapping tool, so differentiation is not an issue and the purpose is unmistakable.

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?

Opens with a rich trigger list ('Use when the user gives or asks about a Singapore postal code, block and street, unit number, or building or place name') plus concrete question archetypes the tool answers. It never names a fallback alternative for non-Singapore or multi-location inputs, only the 'Singapore only' exclusion.

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

All Singapore Buying Desk (Connective Labs) toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources