Skip to main content
Glama

Ready-made deal lists

get_deal_list
Read-onlyIdempotent

A curated list of current Singapore deals: ending-soon (last chance), starting-soon, 1-for-1, free (freebies), birthday (birthday treats), students. Use for questions like 'what deals end this week?' or 'any freebies today?'.

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": {
      "list": "<list>"
    },
    "name": "get_deal_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
listYesWhich list, e.g. ending-soon, 1-for-1 or free. Each list is also a web page at https://spill.sg/deals/<list> (the result's url).
limitNoHow many deals to return (1-50).
budgetNoOptional: low = around S$10 or less, freebies and 1-for-1s first; mid = everyday; high = treats (buffets, staycations) are fine.
trip_endNoOptional YYYY-MM-DD: last day of the visit (with trip_start).
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.
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.
exclude_categoriesNoOptional: categories to leave out entirely, e.g. ['travel', 'property'] for someone who said hotels don't interest them.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / list / enum
      Previous value: -[
      -  "card-1-for-1-buffets",
      -  "weekend-family-dining",
      -  "ending-today",
      -  "ending-soon",
      -  "starting-soon",
      -  "1-for-1",
      -  "new-menu",
      -  "free",
      -  "under-5",
      -  "under-10",
      -  "under-20",
      -  "birthday",
      -  "students",
      -  "tourists",
      -  "this-weekend",
      -  "this-week",
      -  "buffet",
      -  "happy-hour",
      -  "coffee",
      -  "christmas",
      -  "staycation",
      -  "credit-card-sign-up",
      -  "mobile-plans",
      -  "broadband",
      -  "iphone",
      -  "travel-insurance",
      -  "insurance",
      -  "petrol",
      -  "cars",
      -  "cruises",
      -  "flights",
      -  "hotels",
      -  "hotel-buffet",
      -  "seafood-buffet",
      -  "1-for-1-lunch",
      -  "1-for-1-dinner",
      -  "cheap-lunch",
      -  "bubble-tea",
      -  "cafe",
      -  "christmas-dinner",
      -  "black-friday",
      -  "bookstores",
      -  "luggage",
      -  "credit-card",
      -  "citi",
      -  "ocbc",
      -  "dbs",
      -  "uob",
      -  "cashback",
      -  "krisflyer-miles",
      -  "12-12",
      -  "new-years-eve",
      -  "chinese-new-year",
      -  "valentines-day"
      -]New value: +[
      +  "card-1-for-1-buffets",
      +  "weekend-family-dining",
      +  "ending-today",
      +  "ending-soon",
      +  "starting-soon",
      +  "1-for-1",
      +  "new-menu",
      +  "free",
      +  "under-5",
      +  "under-10",
      +  "under-20",
      +  "birthday",
      +  "students",
      +  "tourists",
      +  "this-weekend",
      +  "this-week",
      +  "buffet",
      +  "happy-hour",
      +  "coffee",
      +  "christmas",
      +  "staycation",
      +  "credit-card-sign-up",
      +  "mobile-plans",
      +  "broadband",
      +  "iphone",
      +  "travel-insurance",
      +  "insurance",
      +  "petrol",
      +  "cars",
      +  "cruises",
      +  "flights",
      +  "hotels",
      +  "hotel-buffet",
      +  "seafood-buffet",
      +  "1-for-1-lunch",
      +  "1-for-1-dinner",
      +  "cheap-lunch",
      +  "bubble-tea",
      +  "cafe",
      +  "christmas-dinner",
      +  "online-sales",
      +  "black-friday",
      +  "bookstores",
      +  "luggage",
      +  "credit-card",
      +  "citi",
      +  "ocbc",
      +  "dbs",
      +  "uob",
      +  "hsbc",
      +  "standard-chartered",
      +  "maybank",
      +  "amex",
      +  "trust",
      +  "cimb",
      +  "cashback",
      +  "krisflyer-miles",
      +  "12-12",
      +  "new-years-eve",
      +  "chinese-new-year",
      +  "valentines-day"
      +]
  2. Changed1 schema field changed
    • changedInput schema / properties / list / enum
      Previous value: -[
      -  "card-1-for-1-buffets",
      -  "weekend-family-dining",
      -  "ending-today",
      -  "ending-soon",
      -  "starting-soon",
      -  "1-for-1",
      -  "new-menu",
      -  "free",
      -  "under-5",
      -  "under-10",
      -  "under-20",
      -  "birthday",
      -  "students",
      -  "tourists",
      -  "this-weekend",
      -  "this-week",
      -  "buffet",
      -  "happy-hour",
      -  "coffee",
      -  "christmas",
      -  "staycation",
      -  "credit-card-sign-up",
      -  "mobile-plans",
      -  "broadband",
      -  "iphone",
      -  "travel-insurance",
      -  "insurance",
      -  "petrol",
      -  "cars",
      -  "cruises",
      -  "flights"
      -]New value: +[
      +  "card-1-for-1-buffets",
      +  "weekend-family-dining",
      +  "ending-today",
      +  "ending-soon",
      +  "starting-soon",
      +  "1-for-1",
      +  "new-menu",
      +  "free",
      +  "under-5",
      +  "under-10",
      +  "under-20",
      +  "birthday",
      +  "students",
      +  "tourists",
      +  "this-weekend",
      +  "this-week",
      +  "buffet",
      +  "happy-hour",
      +  "coffee",
      +  "christmas",
      +  "staycation",
      +  "credit-card-sign-up",
      +  "mobile-plans",
      +  "broadband",
      +  "iphone",
      +  "travel-insurance",
      +  "insurance",
      +  "petrol",
      +  "cars",
      +  "cruises",
      +  "flights",
      +  "hotels",
      +  "hotel-buffet",
      +  "seafood-buffet",
      +  "1-for-1-lunch",
      +  "1-for-1-dinner",
      +  "cheap-lunch",
      +  "bubble-tea",
      +  "cafe",
      +  "christmas-dinner",
      +  "black-friday",
      +  "bookstores",
      +  "luggage",
      +  "credit-card",
      +  "citi",
      +  "ocbc",
      +  "dbs",
      +  "uob",
      +  "cashback",
      +  "krisflyer-miles",
      +  "12-12",
      +  "new-years-eve",
      +  "chinese-new-year",
      +  "valentines-day"
      +]
  3. Changed1 schema field changed
    • changedInput schema / properties / list / enum
      Previous value: -[
      -  "ending-today",
      -  "ending-soon",
      -  "starting-soon",
      -  "1-for-1",
      -  "new-menu",
      -  "free",
      -  "under-5",
      -  "under-10",
      -  "under-20",
      -  "birthday",
      -  "students",
      -  "tourists",
      -  "this-weekend",
      -  "this-week",
      -  "buffet",
      -  "happy-hour",
      -  "coffee",
      -  "christmas",
      -  "staycation",
      -  "credit-card-sign-up",
      -  "mobile-plans",
      -  "broadband",
      -  "iphone",
      -  "travel-insurance",
      -  "insurance",
      -  "petrol",
      -  "cars",
      -  "cruises",
      -  "flights"
      -]New value: +[
      +  "card-1-for-1-buffets",
      +  "weekend-family-dining",
      +  "ending-today",
      +  "ending-soon",
      +  "starting-soon",
      +  "1-for-1",
      +  "new-menu",
      +  "free",
      +  "under-5",
      +  "under-10",
      +  "under-20",
      +  "birthday",
      +  "students",
      +  "tourists",
      +  "this-weekend",
      +  "this-week",
      +  "buffet",
      +  "happy-hour",
      +  "coffee",
      +  "christmas",
      +  "staycation",
      +  "credit-card-sign-up",
      +  "mobile-plans",
      +  "broadband",
      +  "iphone",
      +  "travel-insurance",
      +  "insurance",
      +  "petrol",
      +  "cars",
      +  "cruises",
      +  "flights"
      +]
  4. Changed7 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 / 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 / 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 / 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"
      +}
  5. Changed1 schema field changed
    • changedInput schema / properties / list / description
      Previous value: -"Which list, e.g. ending-soon, 1-for-1 or free."New value: +"Which list, e.g. ending-soon, 1-for-1 or free. Each list is also a web page at https://spill.sg/deals/<list> (the result's url)."
  6. Changed3 schema fields changed
    • addedInput schema / properties / limit / description
      Added value: +"How many deals to return (1-50)."
    • addedInput schema / properties / list / description
      Added value: +"Which list, e.g. ending-soon, 1-for-1 or free."
    • changedInput schema / properties / list / enum
      Previous value: -[
      -  "ending-today",
      -  "ending-soon",
      -  "starting-soon",
      -  "1-for-1",
      -  "new-menu",
      -  "free",
      -  "under-5",
      -  "under-10",
      -  "under-20",
      -  "birthday",
      -  "students",
      -  "tourists",
      -  "this-weekend",
      -  "this-week",
      -  "credit-card-sign-up",
      -  "mobile-plans",
      -  "broadband",
      -  "iphone",
      -  "travel-insurance",
      -  "insurance",
      -  "petrol",
      -  "cars",
      -  "cruises",
      -  "flights"
      -]New value: +[
      +  "ending-today",
      +  "ending-soon",
      +  "starting-soon",
      +  "1-for-1",
      +  "new-menu",
      +  "free",
      +  "under-5",
      +  "under-10",
      +  "under-20",
      +  "birthday",
      +  "students",
      +  "tourists",
      +  "this-weekend",
      +  "this-week",
      +  "buffet",
      +  "happy-hour",
      +  "coffee",
      +  "christmas",
      +  "staycation",
      +  "credit-card-sign-up",
      +  "mobile-plans",
      +  "broadband",
      +  "iphone",
      +  "travel-insurance",
      +  "insurance",
      +  "petrol",
      +  "cars",
      +  "cruises",
      +  "flights"
      +]
  7. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent and non-destructive behavior, so the safety profile is covered. The description adds genuinely useful context the annotations do not: each list maps to a web page at spill.sg/deals/<list> returned as the result's url, and that optional personalization inputs (age_range, life_stage) are not stored. It says nothing about ordering, pagination or what a deal record contains, leaving return behavior opaque.

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?

Two sentences, front-loaded with the purpose before the example queries. The inline enumeration of list themes partly duplicates the schema enum, which is mild redundancy against an otherwise tight definition.

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

Completeness4/5

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

For a 9-parameter tool with no output schema, the definition plus a fully documented schema and complete annotations cover what an agent needs to call it correctly. The main residual gap is that ranking behavior from life_stage/interests is only described in the schema, not surfaced in the description's framing.

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?

Schema description coverage is 100%, so baseline is 3; every parameter including budget, life_stage and interests is already documented in the schema with enums. The description adds no further parameter meaning beyond restating a few example list values that the schema enum already contains.

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 the resource (curated deals for Singapore) and enumerates the themed lists it serves, so an agent knows this is a themed browsing tool rather than a query tool. It never names the sibling tools (search_promotions, recommend_promotions, get_promotion), so differentiation from them is implied rather than stated.

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 questions like 'what deals end this week?' and 'any freebies today?', which anchors the tool to browsing-style requests. It stops short of stating when to prefer search_promotions or recommend_promotions instead, so the exclusion side is missing.

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