Skip to main content
Glama

Polymarket Smart Money Signals

pm_signals

Aggregate whale wallet activity to get directional trading signals for Polymarket markets. Shows where top traders are positioning.

Instructions

Get smart money flow signals showing where top traders are positioning. Aggregates whale wallet activity into directional signals per market. Cost: $0.02 per query. Source: Polymarket on-chain data.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
market_idNoFilter by market ID
min_confidenceNoMinimum signal confidence (0-1, default 0.5)
limitNoMaximum results (default 25)

Implementation Reference

  • The handler/executor function for 'pm_signals'. Calls apiGet to /api/v1/pm/signals with market_id, min_confidence, and limit parameters, then formats the response with count and data.
      async ({ market_id, min_confidence, limit }) => {
        const res = await apiGet<PmQueryResponse>("/api/v1/pm/signals", {
          market_id,
          min_confidence: min_confidence ?? 0.5,
          limit: limit ?? 25,
        });
    
        if (!res.ok) {
          return {
            content: [
              {
                type: "text" as const,
                text: `API error (${res.status}): ${JSON.stringify(res.data)}`,
              },
            ],
            isError: true,
          };
        }
    
        const { count, data } = res.data;
        const warn = stalenessWarning(res);
        const summary = `${warn}Found ${count} smart money signal(s).`;
        const json = JSON.stringify(data, null, 2);
    
        return {
          content: [{ type: "text" as const, text: `${summary}\n\n${json}` }],
        };
      },
    );
  • The inputSchema for 'pm_signals' defines three optional parameters: market_id (string), min_confidence (number 0-1, default 0.5), and limit (int 1-100, default 25).
    {
      title: "Polymarket Smart Money Signals",
      description:
        "Get smart money flow signals showing where top traders are positioning. " +
        "Aggregates whale wallet activity into directional signals per market. " +
        "Cost: $0.02 per query. Source: Polymarket on-chain data.",
      inputSchema: {
        market_id: z
          .string()
          .optional()
          .describe("Filter by market ID"),
        min_confidence: z
          .number()
          .min(0)
          .max(1)
          .optional()
          .describe("Minimum signal confidence (0-1, default 0.5)"),
        limit: z
          .number()
          .int()
          .min(1)
          .max(100)
          .optional()
          .describe("Maximum results (default 25)"),
      },
    },
  • src/tools/pm.ts:90-91 (registration)
    The tool is registered with the MCP server via server.registerTool('pm_signals', ...) in the registerPmTools function.
    server.registerTool(
      "pm_signals",
  • src/index.ts:54-58 (registration)
    The registerPmTools function is invoked during MCP server setup in src/index.ts, which registers all PM tools including pm_signals.
    registerPmTools(server);
    registerPmArbTools(server);
    registerPmResolutionTools(server);
    registerEconTools(server);
    registerPmMicroTools(server);
  • The stalenessWarning helper function used by the pm_signals handler to append a staleness warning to the output if the data is stale.
    export function stalenessWarning(res: ApiResponse): string {
      if (!res.stale) return "";
      const parts = ["[STALE DATA]"];
      if (res.lastUpdated) parts.push(`Last updated: ${res.lastUpdated}`);
      if (res.ageSeconds != null) parts.push(`Age: ${res.ageSeconds}s`);
      return parts.join(" ") + "\n\n";
    }
Behavior3/5

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

No annotations provided, so description carries full burden. It mentions cost per query and on-chain source but lacks details on data freshness, rate limits, or interpretation of confidence scores. Behavioral traits are partially disclosed but not comprehensively.

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 concise with three sentences: purpose, aggregation detail, and cost/source. No redundant information, each sentence adds value. Front-loaded with the main action.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given no output schema, the description should explain return values, but it only mentions 'directional signals per market' without specifying fields or structure. It is adequate for a simple query tool but incomplete regarding output format. Parameters are well-covered.

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?

Input schema has 100% description coverage for all three parameters, each with clear descriptions. The tool description does not add additional meaning beyond what the schema already provides, so baseline 3 is appropriate.

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?

Description clearly states the tool provides smart money flow signals showing top trader positioning, with a specific verb 'Get' and resource 'signals'. It distinguishes from siblings like pm_whales and pm_stats by focusing on aggregated directional signals per market.

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 mentions cost and source but does not provide explicit guidance on when to use this tool versus alternatives. Sibling tools exist (pm_whales, pm_stats, etc.) but no when-to-use or when-not-to-use context is given.

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/carrierone/verilexdata-mcp'

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