Skip to main content
Glama

get_edge_opportunities

Identify mispriced Polymarket prediction markets by comparing AI probability analysis with current market prices to find profitable trading opportunities.

Instructions

Find mispriced Polymarket prediction markets where AI analysis disagrees with current market probability. Returns top edge opportunities with recommended positions.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
min_edgeNoMinimum edge percentage to include (default: 5)
limitNoMaximum number of opportunities to return (default: 10)

Implementation Reference

  • Handler implementation for get_edge_opportunities tool. It calls the external LPXPoly API to fetch edge opportunities and formats the output for the user.
    case "get_edge_opportunities": {
      const { min_edge, limit } = args as any;
    
      const result = await callLPXPoly("/api/analyze", {
        type: "edge",
        min_edge: min_edge || 5,
        limit: limit || 10,
      });
    
      const opportunities = result.opportunities || result;
      if (!opportunities?.length) {
        return {
          content: [{ type: "text", text: "No edge opportunities found at this time." }],
        };
      }
    
      const formatted = opportunities
        .map(
          (o: any, i: number) =>
            `${i + 1}. ${o.question || o.market}\n   Market: ${(o.market_prob * 100).toFixed(1)}% | AI: ${(o.ai_prob * 100).toFixed(1)}% | Edge: ${(o.edge * 100).toFixed(1)}%\n   Recommendation: ${o.recommendation || (o.ai_prob > o.market_prob ? "YES" : "NO")}`
        )
        .join("\n\n");
    
      return {
        content: [
          {
            type: "text",
            text: `📊 LPXPoly Edge Opportunities\n\n${formatted}\n\n⚡ Powered by LPXPoly | lpxpoly.com`,
          },
        ],
      };
    }
  • Definition and input schema for the get_edge_opportunities tool.
    {
      name: "get_edge_opportunities",
      description:
        "Find mispriced Polymarket prediction markets where AI analysis disagrees with current market probability. Returns top edge opportunities with recommended positions.",
      inputSchema: {
        type: "object",
        properties: {
          min_edge: {
            type: "number",
            description: "Minimum edge percentage to include (default: 5)",
            default: 5,
          },
          limit: {
            type: "number",
            description: "Maximum number of opportunities to return (default: 10)",
            default: 10,
          },
        },
        required: [],
      },
    },
Behavior3/5

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

With no annotations provided, the description carries the full burden. It discloses the tool's purpose (finding mispriced markets with AI disagreement) and output (top edge opportunities with positions), but lacks details on behavioral traits like rate limits, authentication needs, or what 'mispriced' entails operationally. It adds basic context but misses deeper behavioral insights.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is front-loaded and highly concise—two sentences with zero waste. The first sentence defines the purpose and scope, and the second specifies the return value, making it efficient and easy to parse.

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?

Given the tool's moderate complexity (2 parameters, no output schema, no annotations), the description is reasonably complete. It covers the purpose, output, and high-level logic (AI vs. market probability), but could benefit from more detail on behavioral aspects or output structure to fully compensate for the lack of annotations and output schema.

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 schema fully documents both parameters. The description does not add any parameter-specific meaning beyond what the schema provides (e.g., it doesn't explain 'edge percentage' in more detail or how 'limit' interacts with ranking). Baseline 3 is appropriate as the schema handles 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?

The description clearly states the specific action ('Find mispriced Polymarket prediction markets') and resource ('edge opportunities'), distinguishing it from siblings like 'analyze_market' or 'get_top_markets' by emphasizing AI-disagreement analysis and recommended positions. It goes beyond a simple list to identify mispriced opportunities.

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

Usage Guidelines3/5

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

The description implies usage when seeking mispriced markets based on AI analysis, but does not explicitly state when to use this tool versus alternatives like 'analyze_market' or 'get_top_markets'. No exclusions or prerequisites are mentioned, leaving some ambiguity about optimal context.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/unixlamadev-spec/lpxpoly-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server