Skip to main content
Glama

Search Singapore deals

search_promotions
Read-onlyIdempotent

Find current promotions in Singapore (1-for-1s, discounts, freebies, cashback). Use when someone asks 'any deals on X?', 'what's on promotion this weekend?', or about a brand. Returns deals that have not ended, with dates in Singapore time, conditions and the original source link. If you already know who the person is (student, working adult, parent, senior, visitor, rough age, budget, what they like or don't), pass life_stage / age_range / budget / interests / exclude_categories so the best fits come first, each with a short reason; nothing is stored. Don't ask the person just to fill these in.

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

Input Schema

NameRequiredDescriptionDefault
latNoOptional latitude, to rank nearby deals higher (with lng).
lngNoOptional longitude, with lat.
areaNoInstead of lat/lng: an MRT area, mall or campus name, e.g. 'Tampines', 'Orchard', 'Jewel', 'NUS', 'NTU', 'SMU', 'Ngee Ann Poly'. Unknown names return an error; then pass lat/lng.
sortNonewest (default) = latest announced first. top = best picks: fits the meal, ends soon, has a photo, nearby. for_you = top picks that also fit life_stage / age_range / budget / interests (the default when any of those is given).
whenNoOnly deals usable then, Singapore time, reading each deal's hours (e.g. 'Weekdays 3pm-5pm'). 'dinner tonight' = intent dinner + when tonight.
brandNoBrand name or slug, e.g. 'McDonald's'.
limitNoHow many deals to return (1-50).
queryNoWords to match in brand, deal title, summary or outlet, e.g. 'bubble tea' or 'Jewel'.
budgetNoOptional: low = around S$10 or less, freebies and 1-for-1s first; mid = everyday; high = treats (buffets, staycations) are fine.
intentNoWhat the person wants: breakfast, lunch, dinner, coffee (coffee, bubble tea, desserts), drinks, shopping, fun, money (cards & banks).
statusNolive = on now, ends_today, starting_soon = within 7 days.
categoryNoKind of deal.
trip_endNoOptional YYYY-MM-DD: last day of the visit (with trip_start).
active_onNoOnly deals valid on this Singapore date (YYYY-MM-DD).
age_rangeNoOptional: the person's age range, if known. Used only when life_stage is not given (18_24 leans student, 55_plus leans senior); under_18 also sinks alcohol deals. Not stored.
deal_typeNoe.g. one_for_one for 1-for-1 deals.
interestsNoOptional: what they like. Category keys (food, grocery, shopping, fashion, beauty, health, electronics, home, entertainment, travel, finance, insurance, telco, car, property, education) or finer words (bubble_tea, coffee, desserts, fast_food, buffet, korean, japanese, drinks, movies, kids, fitness, staycation, gadgets). Matching deals rank first.
life_stageNoOptional: who the deals are for, if you already know it from the conversation (never ask just for this). student, working, family (parents with kids), senior, tourist (visiting Singapore). Ranks fitting deals first, e.g. student = cheap food, bubble tea, student discounts first; hotels, cards and insurance later. tourist = deals a visitor can use (no Singapore bank card, residency or local scheme needed) first, attractions and Changi Airport deals up, and each deal gets tourist_fit {usable: yes|maybe|no, needs}. Not stored.
trip_startNoOptional YYYY-MM-DD (Singapore): first day of a visit or of the dates they care about. With trip_end, only deals valid on at least one of those days are returned.
eligibilityNoOnly deals limited to this group, e.g. student for student-only deals.
exclude_categoriesNoOptional: categories to leave out entirely, e.g. ['travel', 'property'] for someone who said hotels don't interest them.
exclude_eligibilityNoLeave out deals limited to these groups, e.g. ['student'] for someone who is not a student. Each deal's `eligibility` lists its groups (empty = anyone).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / intent / enum
      Previous value: -[
      -  "breakfast",
      -  "lunch",
      -  "dinner",
      -  "coffee",
      -  "drinks",
      -  "shopping",
      -  "fun",
      -  "money"
      -]New value: +[
      +  "breakfast",
      +  "lunch",
      +  "dinner",
      +  "coffee",
      +  "drinks",
      +  "birthday",
      +  "shopping",
      +  "fun",
      +  "money"
      +]
  2. Changed12 schema fields changed
    • addedInput schema / properties / age_range
      Added value: +{
      +  "description": "Optional: the person's age range, if known. Used only when life_stage is not given (18_24 leans student, 55_plus leans senior); under_18 also sinks alcohol deals. Not stored.",
      +  "enum": [
      +    "under_18",
      +    "18_24",
      +    "25_34",
      +    "35_44",
      +    "45_54",
      +    "55_plus"
      +  ],
      +  "type": "string"
      +}
    • addedInput schema / properties / area
      Added value: +{
      +  "description": "Instead of lat/lng: an MRT area, mall or campus name, e.g. 'Tampines', 'Orchard', 'Jewel', 'NUS', 'NTU', 'SMU', 'Ngee Ann Poly'. Unknown names return an error; then pass lat/lng.",
      +  "type": "string"
      +}
    • addedInput schema / properties / budget
      Added value: +{
      +  "description": "Optional: low = around S$10 or less, freebies and 1-for-1s first; mid = everyday; high = treats (buffets, staycations) are fine.",
      +  "enum": [
      +    "low",
      +    "mid",
      +    "high"
      +  ],
      +  "type": "string"
      +}
    • addedInput schema / properties / exclude_categories
      Added value: +{
      +  "description": "Optional: categories to leave out entirely, e.g. ['travel', 'property'] for someone who said hotels don't interest them.",
      +  "items": {
      +    "enum": [
      +      "food",
      +      "grocery",
      +      "shopping",
      +      "fashion",
      +      "beauty",
      +      "health",
      +      "electronics",
      +      "home",
      +      "entertainment",
      +      "travel",
      +      "finance",
      +      "insurance",
      +      "telco",
      +      "car",
      +      "property",
      +      "education"
      +    ],
      +    "type": "string"
      +  },
      +  "type": "array"
      +}
    • addedInput schema / properties / interests
      Added value: +{
      +  "description": "Optional: what they like. Category keys (food, grocery, shopping, fashion, beauty, health, electronics, home, entertainment, travel, finance, insurance, telco, car, property, education) or finer words (bubble_tea, coffee, desserts, fast_food, buffet, korean, japanese, drinks, movies, kids, fitness, staycation, gadgets). Matching deals rank first.",
      +  "items": {
      +    "enum": [
      +      "food",
      +      "grocery",
      +      "shopping",
      +      "fashion",
      +      "beauty",
      +      "health",
      +      "electronics",
      +      "home",
      +      "entertainment",
      +      "travel",
      +      "finance",
      +      "insurance",
      +      "telco",
      +      "car",
      +      "property",
      +      "education",
      +      "bubble_tea",
      +      "coffee",
      +      "desserts",
      +      "fast_food",
      +      "buffet",
      +      "korean",
      +      "japanese",
      +      "drinks",
      +      "movies",
      +      "kids",
      +      "fitness",
      +      "staycation",
      +      "gadgets"
      +    ],
      +    "type": "string"
      +  },
      +  "maxItems": 12,
      +  "type": "array"
      +}
    • addedInput schema / properties / lat
      Added value: +{
      +  "description": "Optional latitude, to rank nearby deals higher (with lng).",
      +  "type": "number"
      +}
    • addedInput schema / properties / life_stage
      Added value: +{
      +  "description": "Optional: who the deals are for, if you already know it from the conversation (never ask just for this). student, working, family (parents with kids), senior, tourist (visiting Singapore). Ranks fitting deals first, e.g. student = cheap food, bubble tea, student discounts first; hotels, cards and insurance later. tourist = deals a visitor can use (no Singapore bank card, residency or local scheme needed) first, attractions and Changi Airport deals up, and each deal gets tourist_fit {usable: yes|maybe|no, needs}. Not stored.",
      +  "enum": [
      +    "student",
      +    "working",
      +    "family",
      +    "senior",
      +    "tourist"
      +  ],
      +  "type": "string"
      +}
    • addedInput schema / properties / lng
      Added value: +{
      +  "description": "Optional longitude, with lat.",
      +  "type": "number"
      +}
    • changedInput schema / properties / sort / description
      Previous value: -"newest (default) = latest announced first. top = best picks: fits the meal, ends soon, has a photo, nearby."New value: +"newest (default) = latest announced first. top = best picks: fits the meal, ends soon, has a photo, nearby. for_you = top picks that also fit life_stage / age_range / budget / interests (the default when any of those is given)."
    • changedInput schema / properties / sort / enum
      Previous value: -[
      -  "newest",
      -  "ending",
      -  "nearest",
      -  "top"
      -]New value: +[
      +  "newest",
      +  "ending",
      +  "nearest",
      +  "top",
      +  "for_you"
      +]
    • addedInput schema / properties / trip_end
      Added value: +{
      +  "description": "Optional YYYY-MM-DD: last day of the visit (with trip_start).",
      +  "type": "string"
      +}
    • addedInput schema / properties / trip_start
      Added value: +{
      +  "description": "Optional YYYY-MM-DD (Singapore): first day of a visit or of the dates they care about. With trip_end, only deals valid on at least one of those days are returned.",
      +  "type": "string"
      +}
  3. Changed1 schema field changed
    • addedInput schema / properties / limit / description
      Added value: +"How many deals to return (1-50)."
  4. First observed

TDQS

A4.3/5.0
Behavior5/5

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

Annotations already establish read-only, idempotent, non-destructive, closed-world behavior, and the description still adds real substance: results exclude ended deals, dates are Singapore time, each deal carries conditions and a source link, personalization inputs are not stored, and an unknown area name returns an error with a lat/lng fallback. That is meaningful operational context beyond the annotation set.

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 purpose, then examples, then return behavior, then personalization guidance — a sensible information order with no filler sentences. It is dense and long, and a few schema-restating clauses about life_stage could be trimmed, but every sentence carries weight.

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?

For a 22-parameter, zero-required search tool with no output schema, the description supplies the missing return-value picture (deal content, conditions, source link, Singapore-time dates) and the failure mode for unresolvable areas. An agent has everything needed to call it correctly and interpret results.

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%, so the baseline is 3 and the schema already documents ranking and filter parameters in depth. The description still contributes by framing the personalization parameters as optional conversational enrichment, noting that fits are ranked first with a short reason, and reinforcing the no-storage guarantee and the error path for unknown areas.

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?

Opens with a specific verb and resource plus concrete scope: 'Find current promotions in Singapore (1-for-1s, discounts, freebies, cashback).' An agent immediately knows this is deal discovery, not lookup-by-id or brand listing. It doesn't explicitly distinguish itself from siblings like nearby_promotions or recommend_promotions, so it falls short of a 5.

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?

Gives concrete trigger phrasings ('any deals on X?', 'what's on promotion this weekend?', or about a brand) and instructs when to enrich with life_stage/age_range/budget/interests, plus the negative guidance 'Don't ask the person just to fill these in.' Clear context, though it never names which sibling to use for a nearby-only or recommendation-style request.

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