Skip to main content
Glama

Prediction Markets Quant

by com.predictionmarketspicks
OverviewDiscussionsAdmin

Scan Mispricings

scan_mispricings
Read-only

Scan Polymarket contracts for mispricings against the PMP model (a probability swarm). Returns each market where the model disagrees with the price, the direction to take, the edge in percentage points, and quarter-Kelly sizing, sorted by absolute edge. The scanner is being rebuilt for the 2026 midterms and usually returns no rows today; the response says when it last ran. Pro — sign in with PredictionMarketsPicks, or a Pro API key. Use for "where is the edge today", "mispriced markets", "what should I trade".

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoMax rows to return (default 10). Values above 25 are clamped to 25.
minEdgeNoMinimum absolute edge in pp to include (default 5). Accepts a number or a numeric string ("3", "3pp", "3%").

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 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"
+]
    • removedInput schema / properties / minEdge / anyOf
      Removed value: -[
-  {
-    "type": "number"
-  },
-  {
-    "type": "string"
-  }
-]
    • addedInput schema / properties / minEdge / type
      Added value: +[
+  "number",
+  "string"
+]
  2. 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: -10
    • changedInput schema / properties / limit / description
      Previous value: -"Max rows to return (default 10)."New value: +"Max rows to return (default 10). Values above 25 are clamped to 25."
    • removedInput schema / properties / limit / maximum
      Removed value: -25
    • removedInput schema / properties / limit / minimum
      Removed value: -1
    • removedInput schema / properties / limit / type
      Removed value: -"integer"
  3. First observed

TDQS

A4.4/5.0
Behavior5/5

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

Goes well beyond the readOnly/openWorld annotations by disclosing that the scanner is being rebuilt and usually returns zero rows today, that the response reports the last run time, that results are sorted by absolute edge, and that Pro auth is required. An agent knows both the failure mode and the auth prerequisite before calling.

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 purpose and return shape lead, with the empty-result caveat and auth note following. Every sentence carries information, though the quoted trigger phrases add some length that could be trimmed.

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 describing the returned fields (market, direction, edge, Kelly sizing, sort order, last-run timestamp). Between that and the schema, an agent has everything needed to call and interpret this tool.

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 coverage is 100%, so limit's default/clamp behavior and minEdge's accepted formats ('3', '3pp', '3%') are fully documented in the schema itself. The description adds nothing parameter-specific, which is the expected baseline when the schema does the heavy lifting.

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 — scanning Polymarket contracts for mispricings against the PMP probability-swarm model — and enumerates the output (direction, edge in pp, quarter-Kelly sizing). This is distinguishable from siblings like find_arbitrage or calculate_ev without opening any schema.

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 invocation triggers ('where is the edge today', 'mispriced markets', 'what should I trade') and states the access gate (Pro sign-in or API key). It does not compare itself against alternatives such as find_arbitrage or edge_alerts, so it stops short of explicit when-not guidance.

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