Skip to main content
Glama

Weather Markets Edge Desk

by com.predictionmarketspicks
OverviewDiscussionsAdmin

Edge Alerts (weather / commodity / mispricing)

edge_alerts
Read-only

Use for "any edge on Kalshi" and "weather trade signals". Our model alerts on Kalshi — weather, bitcoin/silver/gold/oil, mispricings — with feed, tier, side, price, model probability, edge and link. Real time with Pro; free is delayed 24h without the thesis. One identical, impersonal feed for every subscriber; filters only select. Informational, not investment advice.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
feedNoComma-separated feeds to include: weather, bitcoin, silver, gold, oil, mispricing, sports_arb, nfl. Omit for all.
limitNoMax alerts to return (default 25). Values above 100 are clamped to 100.
sinceNoISO-8601 timestamp — only alerts created after it.
min_tierNoMinimum confidence tier (returns that tier and above). One of: SPECULATIVE · MODERATE · STRONG.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • removedInput schema / properties / limit / anyOf
      Removed value: -[
-  {
-    "anyOf": [
-      {
-        "type": "number"
-      },
-      {
-        "type": "string"
-      }
-    ]
-  },
-  {
-    "type": "null"
-  }
-]
    • addedInput schema / properties / limit / type
      Added value: +[
+  "number",
+  "string",
+  "null"
+]
  2. Changed4 schema fields changed
    • addedInput schema / properties / min_tier / anyOf
      Added value: +[
+  {
+    "type": "string"
+  },
+  {
+    "enum": [
+      "SPECULATIVE",
+      "MODERATE",
+      "STRONG"
+    ],
+    "type": "string"
+  }
+]
    • changedInput schema / properties / min_tier / description
      Previous value: -"Minimum confidence tier (returns that tier and above)."New value: +"Minimum confidence tier (returns that tier and above). One of: SPECULATIVE · MODERATE · STRONG."
    • removedInput schema / properties / min_tier / enum
      Removed value: -[
-  "SPECULATIVE",
-  "MODERATE",
-  "STRONG"
-]
    • removedInput schema / properties / min_tier / type
      Removed value: -"string"
  3. Changed6 schema fields changed
    • addedInput schema / properties / limit / anyOf
      Added value: +[
+  {
+    "anyOf": [
+      {
+        "type": "number"
+      },
+      {
+        "type": "string"
+      }
+    ]
+  },
+  {
+    "type": "null"
+  }
+]
    • removedInput schema / properties / limit / default
      Removed value: -25
    • changedInput schema / properties / limit / description
      Previous value: -"Max alerts to return (default 25)."New value: +"Max alerts to return (default 25). Values above 100 are clamped to 100."
    • removedInput schema / properties / limit / maximum
      Removed value: -100
    • removedInput schema / properties / limit / minimum
      Removed value: -1
    • removedInput schema / properties / limit / type
      Removed value: -"integer"
  4. First observed

TDQS

A4.1/5.0
Behavior5/5

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

Beyond the readOnly/openWorld annotations, the description discloses tier-gated behavior (real time with Pro, free delayed 24h without the thesis), that the feed is identical and impersonal for every subscriber, that filters only select rather than personalize, and an informational-use disclaimer. These are exactly the behavioral traits annotations cannot carry.

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?

It is front-loaded with the usage trigger and packs payload, tiering, and disclaimers into a few compact sentences. The marketing-toned phrases ('any edge on Kalshi', 'One identical, impersonal feed') add some noise but are short.

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 compensates by enumerating the returned fields and explaining the real-time vs 24h-delayed access model and filter semantics. For a read-only feed with all four params documented in schema, nothing an agent needs to call it correctly is missing.

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 feed, limit, since, and min_tier are already fully documented in the schema. The description's list of 'feed, tier, side, price, model probability, edge and link' describes output fields, not parameter meaning, so it adds nothing to parameter interpretation. Baseline 3 applies.

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?

The description names the resource (Kalshi model alerts) and enumerates the covered categories (weather, bitcoin/silver/gold/oil, mispricings) plus the returned fields, so the agent knows this is a unified alert feed rather than a single-market board. It stops short of explicitly distinguishing itself from near siblings like weather_board, commodity_edge, or scan_mispricings.

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?

It opens with a direct usage trigger — 'Use for "any edge on Kalshi" and "weather trade signals"' — which gives the agent clear context for selection. However, it names no when-not conditions and does not route the agent to or away from the overlapping sibling tools.

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

All Weather Markets Edge Desk 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