Skip to main content
Glama
PaulieB14

graph-polymarket-mcp

get_last_trade

Get the last trade price for a Polymarket outcome token by providing its CLOB token ID.

Instructions

Get the last trade price for a Polymarket outcome token from the CLOB.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
tokenIdYesCLOB token ID

Implementation Reference

  • src/index.ts:1246-1265 (registration)
    Registration of the 'get_last_trade' MCP tool. Defines input schema (tokenId) and handler that calls getClobLastTradePrice.
    // Tool 29: get_last_trade
    // ---------------------------------------------------------------------------
    server.registerTool(
      "get_last_trade",
      {
        description:
          "Get the last trade price for a Polymarket outcome token from the CLOB.",
        inputSchema: {
          tokenId: z.string().describe("CLOB token ID"),
        },
      },
      async ({ tokenId }) => {
        try {
          const result = await getClobLastTradePrice(tokenId);
          return textResult({ tokenId, ...result });
        } catch (error) {
          return errorResult(error);
        }
      }
    );
  • Actual handler/helper function that fetches the last trade price from the CLOB API endpoint /last-trade-price.
    export async function getClobLastTradePrice(
      tokenId: string
    ): Promise<{ price: string }> {
      return fetchJson<{ price: string }>(
        `${CLOB_BASE}/last-trade-price?token_id=${encodeURIComponent(tokenId)}`
      );
    }
  • Generic helper that performs the HTTP fetch and JSON parsing for all CLOB API calls including getClobLastTradePrice.
    async function fetchJson<T>(url: string): Promise<T> {
      const response = await fetch(url, {
        headers: { Accept: "application/json" },
      });
      if (!response.ok) {
        throw new PolymarketApiError(
          `HTTP ${response.status}: ${response.statusText}`,
          response.status,
          url
        );
      }
      return response.json() as Promise<T>;
    }
  • Base URL constant for the CLOB API, used by getClobLastTradePrice to construct the endpoint URL.
    const CLOB_BASE = "https://clob.polymarket.com";
  • src/index.ts:10-24 (registration)
    Import of getClobLastTradePrice from polymarketApi, used in the get_last_trade tool handler.
    import {
      searchMarkets,
      getMarketBySlug,
      getMarketByConditionId,
      listEvents,
      getEvent,
      getClobPrice,
      getClobPricesBatch,
      getClobMidpoint,
      getClobSpread,
      getClobOrderBook,
      getClobLastTradePrice,
      getClobPriceHistory,
      getClobMarket,
    } from "./polymarketApi.js";
Behavior2/5

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

No annotations are provided, and the description does not disclose any behavioral traits such as data freshness, rate limits, error conditions, or whether the price is retrieved from cache or real-time. The description carries the full burden for transparency but only states the action.

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 a single, concise sentence that immediately conveys the tool's purpose without any extraneous information. Every word earns its place.

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 the single parameter, lack of output schema, and no annotations, the description is minimally adequate. However, it lacks details on return format, possible errors, and usage context, which would make it more complete for an agent.

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% with one parameter described as 'CLOB token ID'. The description does not add any additional meaning or context beyond what the schema provides, so a baseline score of 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?

The description clearly states the tool retrieves the last trade price for a Polymarket outcome token, using a specific verb 'Get' and resource 'last trade price'. It distinguishes itself from sibling tools like get_live_prices or get_orderbook_trades by focusing on the last traded price from the CLOB.

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

Usage Guidelines2/5

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

No guidance on when to use this tool versus alternatives like get_live_prices or get_orderbook_trades. It does not mention prerequisites, context, or exclusions, leaving the agent to infer usage from the name alone.

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/PaulieB14/graph-polymarket-mcp'

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