Skip to main content
Glama
Sign In

Prediction Markets Quant

by com.predictionmarketspicks
OverviewDiscussionsAdmin

Edge Alerts (weather / commodity / mispricing)

edge_alerts
Read-only

Use for "any edge on Kalshi", "where is the edge today" 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.

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

Input 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; 4 when the call has no arguments).
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. Changed1 schema field changed
    • changedInput schema / properties / limit / description
      Previous value: -"Max alerts to return (default 25)."New value: +"Max alerts to return (default 25; 4 when the call has no arguments)."
  2. Changed2 schema fields changed
    • removedInput schema / $schema
      Removed value: -"https://json-schema.org/draft/2020-12/schema"
    • changedInput schema / properties / limit / description
      Previous value: -"Max alerts to return (default 25). Values above 100 are clamped to 100."New value: +"Max alerts to return (default 25)."
  3. 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"
+]
  4. 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"
  5. 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"
  6. 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 readOnlyHint, openWorldHint and destructiveHint=false, so the safety profile is covered. The description adds real behavioral context beyond that: real-time delivery requires Pro, free access is delayed 24h and omits the thesis, and the feed is identical and impersonal for every subscriber with filters only selecting. These are useful disclosure points about freshness and personalization, though return format and pagination behavior remain unstated.

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?

The definition is compact and front-loads the trigger queries and covered domains before the delivery and disclaimer notes. A few clauses ("one identical, impersonal feed for every subscriber") are wordy but serve a real purpose in setting expectations.

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?

With four optional parameters, no required inputs and no output schema, the description does the necessary work by listing the alert payload fields and explaining the free/Pro freshness difference. Only the overlap with the weather_board sibling is left unresolved.

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 all four parameters (feed, limit, since, min_tier) are already fully documented with formats, defaults and enum values. The description adds no parameter-level meaning — the field list it cites (tier, side, price, edge) describes returned alerts rather than inputs, so the 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 a specific resource (Kalshi model alerts) and enumerates the covered domains — weather, bitcoin/silver/gold/oil, mispricings — plus the fields returned (feed, tier, side, price, model probability, edge, link). It is clear what the tool returns, but it never distinguishes itself from the sibling weather_board, which appears to overlap on the weather signal domain.

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?

Trigger phrases like "any edge on Kalshi" and "where is the edge today" give concrete when-to-use context, and the Pro/free note sets expectations about freshness. It stops short of stating when NOT to use it or naming weather_board as an alternative for weather-specific questions.

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

All Prediction Markets Quant 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