Skip to main content
Glama
Sign In

WhatsMood

by com.whatsmood
OverviewDiscussionsAdmin

Business campaigns (sponsored)

list_campaigns
Read-onlyIdempotent

Only call when the user explicitly asks for deals, discounts, offers or campaigns; do not suggest campaigns otherwise. Lists active campaigns that venues and brands publish on WhatsMood Business, by city, neighbourhood or mood: business name, offer, description, end date, distance. These are SPONSORED business content: every result has sponsored=true and label 'Business campaign (sponsored)' — show that label to the user. Personal codes are claimed inside the WhatsMood app. TR: İşletme kampanyaları (sponsorlu); yalnız kullanıcı isterse.

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

Input Schema

NameRequiredDescriptionDefault
cityNoCity name, e.g. Istanbul. Optional.
moodNoMood to rank matching campaigns first, e.g. romantic, happy. Optional.
placeNoNeighbourhood or district, e.g. Kadıköy, Beşiktaş. Optional.
latitudeNoOptional latitude (rounded to ~1 km); not required.
longitudeNoOptional longitude (rounded to ~1 km); not required.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • changedInput schema / properties / latitude / description
      Previous value: -"Latitude for nearby deals (with longitude). Optional."New value: +"Optional latitude (rounded to ~1 km); not required."
    • changedInput schema / properties / longitude / description
      Previous value: -"Longitude for nearby deals (with latitude). Optional."New value: +"Optional longitude (rounded to ~1 km); not required."
    • changedInput schema / properties / mood / description
      Previous value: -"Mood to rank matching deals first, e.g. romantic, happy. Optional."New value: +"Mood to rank matching campaigns first, e.g. romantic, happy. Optional."
    • addedInput schema / properties / place
      Added value: +{
+  "default": null,
+  "description": "Neighbourhood or district, e.g. Kadıköy, Beşiktaş. Optional.",
+  "type": [
+    "string",
+    "null"
+  ]
+}
  2. First observed

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive/closed-world, so safety is covered; the description instead adds disclosure obligations the annotations cannot express: every result carries sponsored=true and a 'Business campaign (sponsored)' label that must be shown to the user. It also notes that personal codes are claimed inside the WhatsMood app, which tells the agent the tool cannot complete a redemption. A small gap remains on result volume/pagination.

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 call-gating condition, then scope, then returned fields, then the sponsored-label obligation — a sensible order with no filler. The trailing Turkish line repeats the gating condition for a different audience, which is defensible for a bilingual product but is the one mildly redundant element.

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 burden of describing returns and does so by naming the fields and the mandatory sponsored label. Combined with the usage gate and the note that redemption happens in-app, an agent has everything needed to call this and present results correctly.

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 a 3 is the floor. The description adds a little real meaning by mapping the prose 'neighbourhood' onto the schema's 'place' parameter and framing mood as a ranking input ('by city, neighbourhood or mood'), clarifying that these are optional scoping levers rather than filters. Latitude/longitude are left to the schema, which documents them adequately.

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 and resource ('Lists active campaigns that venues and brands publish on WhatsMood Business') and enumerates the returned fields (business name, offer, description, end date, distance). It also scopes the source by 'by city, neighbourhood or mood', so an agent can distinguish it from event/list/city/mood siblings without opening a schema.

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?

Gives an explicit gating condition — 'Only call when the user explicitly asks for deals, discounts, offers or campaigns' — plus an explicit prohibition: 'do not suggest campaigns otherwise.' This is a when-to-use and when-not-to-use pair, which is rare and directly actionable for an agent deciding between siblings.

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

All WhatsMood 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