Skip to main content
Glama

dayplay-mcp

by io.github.Teamdayplay
OverviewDiscussionsAdmin

get_decision_feed

Ranked decision feed. Send user_lat and user_lng as numbers.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
tzNotz
offsetNooffset
user_latYesDecimal degrees. Send a number, not a string.
user_lngYesDecimal degrees. Send a number, not a string.
radius_kmNoRadius in kilometers. Send a number, not a string.
anchor_cityNoanchor_city
max_resultsNomax_results
weekend_dayNosat or sun.
search_queryNoNatural-language query.
selected_typeNoselected_type
selected_genresNoselected_genres
event_week_offsetNoevent_week_offset
preferred_radius_kmNoRadius in kilometers. Send a number, not a string.
selected_time_bandsNoselected_time_bands
selected_price_tiersNoselected_price_tiers
selected_subcategoriesNoselected_subcategories

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties
      Added value: +{
+  "anchor_city": {
+    "description": "anchor_city",
+    "type": "string"
+  },
+  "event_week_offset": {
+    "description": "event_week_offset",
+    "type": "integer"
+  },
+  "max_results": {
+    "description": "max_results",
+    "type": "integer"
+  },
+  "offset": {
+    "description": "offset",
+    "type": "integer"
+  },
+  "preferred_radius_km": {
+    "description": "Radius in kilometers. Send a number, not a string.",
+    "type": "number"
+  },
+  "radius_km": {
+    "description": "Radius in kilometers. Send a number, not a string.",
+    "type": "number"
+  },
+  "search_query": {
+    "description": "Natural-language query.",
+    "type": "string"
+  },
+  "selected_genres": {
+    "description": "selected_genres",
+    "items": {
+      "type": "string"
+    },
+    "type": "array"
+  },
+  "selected_price_tiers": {
+    "description": "selected_price_tiers",
+    "items": {
+      "type": "integer"
+    },
+    "type": "array"
+  },
+  "selected_subcategories": {
+    "description": "selected_subcategories",
+    "items": {
+      "type": "string"
+    },
+    "type": "array"
+  },
+  "selected_time_bands": {
+    "description": "selected_time_bands",
+    "items": {
+      "type": "string"
+    },
+    "type": "array"
+  },
+  "selected_type": {
+    "description": "selected_type",
+    "type": "string"
+  },
+  "tz": {
+    "description": "tz",
+    "type": "string"
+  },
+  "user_lat": {
+    "description": "Decimal degrees. Send a number, not a string.",
+    "type": "number"
+  },
+  "user_lng": {
+    "description": "Decimal degrees. Send a number, not a string.",
+    "type": "number"
+  },
+  "weekend_day": {
+    "description": "sat or sun.",
+    "enum": [
+      "sat",
+      "sun"
+    ],
+    "type": "string"
+  }
+}
    • addedInput schema / required
      Added value: +[
+  "user_lat",
+  "user_lng"
+]
  2. Added

TDQS

C2.3/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full behavioral burden, yet it discloses nothing about read-only safety, authentication, rate limits, or what the "ranked" ordering is based on. It does at least imply a read operation returning ranked items, which is slightly more than nothing.

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?

The description is short and front-loaded, which is good, but the second sentence merely repeats what the schema already says, so it does not earn its place. Two sentences, one of which is wasted.

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

Completeness2/5

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

With 16 parameters, no annotations, and no output schema, the description should explain the feed's nature, ranking, and pagination (offset, max_results) behavior, but it covers none of this. For a tool of this complexity it is materially under-specified.

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 the baseline is 3. The description's only parameter remark ("Send user_lat and user_lng as numbers") duplicates the schema text verbatim ("Decimal degrees. Send a number, not a string."), adding no new meaning.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose2/5

Does the description clearly state what the tool does and how it differs from similar tools?

"Ranked decision feed" is essentially a restatement of the tool name get_decision_feed, with only the word "ranked" adding marginal information. There is no verb describing the action and no statement of what the feed actually contains or returns, so an agent cannot distinguish it from siblings like get_events, get_weekend, or get_local_gems.

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

Usage Guidelines2/5

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

The only guidance given is argument formatting ("Send user_lat and user_lng as numbers"), which is parameter hygiene rather than usage guidance. Nothing states when to use this tool versus the many feed-like siblings, nor any prerequisite or exclusion.

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

All dayplay-mcp 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