Skip to main content
Glama
Sign In

Singapore Event Print & Merch Quotes

by io.github.connectivehub
OverviewDiscussionsAdmin
This connector has been deprecated

Renamed to Singapore Buying Desk. Replaced by https://glama.ai/mcp/connectors/com.connective-labs/sg-buying-desk.

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. Example input: {"task":"renew my passport"}.

Input 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.3/5.0
Behavior5/5

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

Beyond the annotations, the description provides critical behavior not in the schema, such as returning the 'best 1 to 3 matches', providing a 'source_url and last_checked' timestamp, and labeling uncertain agency suggestions as 'guesses'.

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?

While all information is present, the definition is overly verbose. It lists nearly every possible covered topic (passports, GST, HDB, vehicles, etc.) in a dense paragraph, sacrificing conciseness for comprehensive coverage.

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?

Given the wide range of topics it covers (from taxes to public housing to customs), the definition is remarkably complete. It defines the output format (1-3 matches), the limitations of the data, and explicitly states its 'read-only' nature and coverage limitations.

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?

The input schema description is already very rich, providing multiple detailed examples of valid task strings. The description reiterates the 'task' nature but does not add semantic depth or constraints beyond what is provided in the schema or annotations.

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?

The purpose is perfectly clear: providing instructions on how to execute errands or government processes. It immediately establishes the specific geographical scope (Singapore) and the intended audience.

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?

The description explicitly sets boundaries by stating it is 'Singapore only' and excludes general recommendations (restaurants/sights). It clearly defines when it is appropriate—when an official process or specific task needs to be researched.

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

All Singapore Event Print & Merch Quotes 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