Skip to main content
Glama

get_pools

Retrieve open competition pools with win probabilities, shares, prices, and conviction data to inform entry decisions for strategy-based revenue capture.

Instructions

Get all currently open pools with win probabilities, pool shares, prices, time remaining, and conviction multiplier info. Use this to decide which pools to enter.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The implementation of the `get_pools` tool, which fetches open pool data from the API and formats it into a markdown string for the MCP client.
    // ── Tool: get_pools ──
    
    server.tool(
      "get_pools",
      "Get all currently open pools with win probabilities, pool shares, prices, time remaining, and conviction multiplier info. Use this to decide which pools to enter.",
      {},
      async () => {
        const data = (await apiGet("pool-state?mode=open")) as any;
        const pools = data.pools || [];
    
        if (pools.length === 0) {
          return {
            content: [
              { type: "text", text: "No open pools right now. Pools open daily at 10:00 UTC." },
            ],
          };
        }
    
        const lines = pools.map((p: any) => {
          const aId = p.tokenA?.id ?? "?";
          const bId = p.tokenB?.id ?? "?";
          const hrs = p.hoursRemaining?.toFixed(1) ?? "?";
          const total = p.totalPoolUsdc?.toFixed(0) ?? "?";
    
          const aProb = p.tokenA?.winProbability != null ? p.tokenA.winProbability.toFixed(1) : null;
          const bProb = p.tokenB?.winProbability != null ? p.tokenB.winProbability.toFixed(1) : null;
          const aShare = p.tokenA?.poolSharePercent?.toFixed(1) ?? "50.0";
          const bShare = p.tokenB?.poolSharePercent?.toFixed(1) ?? "50.0";
          const aStart = p.tokenA?.startPrice ? `$${p.tokenA.startPrice.toFixed(2)}` : "—";
          const bStart = p.tokenB?.startPrice ? `$${p.tokenB.startPrice.toFixed(2)}` : "—";
    
          // Conviction multiplier context
          const timeRatio = p.convictionInfo?.currentTimeRatio ?? 0;
          const multHint = timeRatio <= 0 ? "1.0x (early bonus)" : timeRatio >= 0.8 ? "penalized for late entries on favorites" : `time ratio ${timeRatio.toFixed(2)}`;
    
          const probLine = aProb && bProb
            ? `  Win probability: ${aId} ${aProb}% / ${bId} ${bProb}%`
            : `  Win probability: pending (updates every 5 min)`;
    
          return [
            `**${p.tokenPairKey}** — ${hrs}h left, $${total} pool`,
            probLine,
            `  ${aId}: ${aShare}% pool ($${p.tokenA?.poolAmount?.toFixed(0) ?? 0}) | open ${aStart}`,
            `  ${bId}: ${bShare}% pool ($${p.tokenB?.poolAmount?.toFixed(0) ?? 0}) | open ${bStart}`,
            `  Conviction: ${multHint}`,
          ].join("\n");
        });
    
        return {
          content: [
            {
              type: "text",
              text: `# Open Pools (${pools.length})\n\n${lines.join("\n\n")}\n\n_Fetched at ${new Date().toISOString()}_\n_Win probability = computed from live price momentum (updated every 5 min). Pool share = money distribution (payout odds). Use enter_position to enter a pool, or create_agent for automatic strategy execution._`,
            },
          ],
        };
      }
    );
Behavior3/5

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

No annotations are provided, so the description carries the full burden. It describes what data is returned but doesn't disclose behavioral traits like rate limits, authentication requirements, pagination, or error conditions. The description adds value by specifying the data fields returned, but lacks operational context.

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 two concise sentences with zero waste. The first sentence clearly states what the tool does and what data it returns. The second sentence provides explicit usage guidance. Both sentences earn their place by adding value beyond the tool name.

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 simplicity (0 parameters, no output schema, no annotations), the description is reasonably complete. It explains what data is returned and when to use it. However, without annotations or output schema, it could benefit from more detail about return format or behavioral constraints, though this is less critical for a read-only list tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool has 0 parameters with 100% schema description coverage. The description doesn't need to explain parameters, and it appropriately focuses on the tool's purpose and usage. A baseline of 4 is appropriate for a zero-parameter tool where the schema fully documents the absence of inputs.

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 verb ('Get') and resource ('all currently open pools') with specific details about what information is retrieved (win probabilities, pool shares, prices, time remaining, conviction multiplier info). It distinguishes this tool from siblings like 'get_pool_history' (historical data) and 'enter_position' (action tool).

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

Usage Guidelines5/5

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

The description explicitly states when to use this tool: 'Use this to decide which pools to enter.' This provides clear guidance on its purpose in the workflow context and distinguishes it from alternatives like 'get_pool_history' (for past data) or 'get_my_agents' (for agent status).

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/abcxz/conviction-fm'

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