Skip to main content
Glama

Singapore Buying Desk (Connective Labs)

by com.connective-labs
OverviewDiscussionsAdmin

How to get an errand or government process done in Singapore

singapore_how_to
Read-onlyIdempotent

Use for an errand, government process or practical how-to in Singapore, for residents, employers and visitors. It says which agency or type of business handles the task, the official channel and URL, whether Singpass, Corppass or a UEN is needed, whether it is fully online or needs a visit, fees and processing times only where the official page states them, whether an agent can act or must hand off to the user (login, app or phone), the next step, and any related API or MCP tool. Covers, among others: passports, NRIC and change of address; visas, the SG Arrival Card, tourist GST refunds at the airport, paying for MRT and buses as a visitor, SIM cards at Changi; personal and company income tax, GST registration, company and business registration and annual filing; work passes and domestic helper permits (new and renewal); HDB matters such as season parking, bulky item disposal, home-based businesses and neighbour or smoking complaints; municipal issues, police reports, scams, vehicles, road tax and parking; utilities, CPF, healthcare appointments, ActiveSG court bookings, school registration, pets; sending parcels; and buying office supplies or event print. Returns the best 1 to 3 matches from a list checked against official pages, each with source_url and last_checked. Says plainly when a task is not covered, and labels any agency suggestion for it as a guess. Singapore only; not for other countries, and not for recommendations such as restaurants or sights. Read-only.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
taskYesThe task in the user's own plain words, one task per call, e.g. 'renew my passport', 'get rid of an old mattress from my HDB flat', 'claim GST refund at the airport as a tourist', 'file corporate tax for my company', 'book a tennis court'.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / task / description
      Previous value: -"The errand in plain words, e.g. 'renew passport', 'dispose of an old sofa', 'book a badminton court'."New value: +"The task in the user's own plain words, one task per call, e.g. 'renew my passport', 'get rid of an old mattress from my HDB flat', 'claim GST refund at the airport as a tourist', 'file corporate tax for my company', 'book a tennis court'."
  2. Added

TDQS

A4.8/5.0
Behavior5/5

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

Annotations cover the safety profile (readOnly, idempotent, non-destructive, closed-world), and the description adds substantial behavior beyond them: returns 1-3 matches with source_url and last_checked, discloses uncertainty by flagging guesswork for uncovered tasks, and explains agent-vs-user hand-off. This is rich disclosure layered on top of annotations.

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-loads the use case and the return contract before the long coverage inventory, and the inventory does earn its place for retrieval routing. However, the mid-section is a dense run-on list that would read better as bullets, costing some scannability.

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 carries the full burden and does so: it specifies the returned fields (source_url, last_checked), the match count (1-3), the 'not covered' behavior, and the guess-labelling. Nothing material is missing for correct invocation.

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

Parameters4/5

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

Schema coverage is 100% and the schema already shows example task strings, so baseline is 3. The description adds value by enumerating the domains of valid tasks (passports, tax, work passes, HDB, etc.), which helps an agent frame the free-text 'task' argument correctly, though it does not define syntax beyond that.

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 function (find how to get a Singapore errand/government process done) and enumerates the exact domain coverage, so an agent can tell it apart from the quote/address siblings at a glance. The scope is bounded (Singapore only) and the output shape (best 1-3 matches) is named.

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

Usage Guidelines5/5

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

Explicitly says who it is for (residents, employers, visitors), what it returns, and gives clear exclusions: 'Singapore only; not for other countries, and not for recommendations such as restaurants or sights.' The alternative-use boundary is stated rather than inferred.

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