Skip to main content
Glama
Sign In
fin-data-mcp-server

fin-data-mcp-server

by CohenD
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Polymarket last trade price (CLOB)

polymarket_last_trade_price
Read-onlyIdempotent

Retrieve the last trade price and trade side for a Polymarket outcome token by specifying its CLOB token ID.

Instructions

Most recent trade price and side for an outcome token. token_id is a CLOB token id from a market's clobTokenIds. Example: { token_id: "98022490269692409998126496127597032490334070080325855126491859374983463996227" }

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "token_id": "<token_id>"
    },
    "name": "polymarket_last_trade_price"
  }
}

Input Schema

NameRequiredDescriptionDefault
token_idYesCLOB token id

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A4/5.0
Behavior3/5

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

Annotations already provide readOnlyHint, idempotentHint, destructiveHint. Description adds that it returns 'price and side' but doesn't go beyond that. No contradiction.

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?

One sentence plus an example. Extremely concise, front-loaded with purpose, no redundant words.

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 simple tool (one param, good annotations, no output schema), the description provides enough context: what it returns and example input. Could note response format but not critical.

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?

Schema covers the parameter with description 'CLOB token id'. Description adds a concrete example token_id, which helps the agent understand the required format and length.

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?

Clearly states it returns the most recent trade price and side for a CLOB token id. Distinguishes from siblings like polymarket_price_history or polymarket_get_market by focusing on the last trade price.

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?

Implies usage when needing the last trade price, but no explicit guidance on when to use this tool versus alternatives among the many sibling tools. No exclusions or alternative recommendations.

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

Deploy Server

Other Tools