Skip to main content
Glama
Sign In
MicroTap-MCP

MicroTap-MCP

by swaltersjrtest
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Single Polymarket market detail

get_polymarket_market
Read-onlyIdempotent

Get a Polymarket market's full data by slug: price, 24h, weekly, total volume, liquidity, and resolution status. Analyze or monitor specific prediction markets.

Instructions

Full detail for a single Polymarket market by slug: prices, volume (24h/1wk/total), liquidity, resolution status. Price: $0.002 per call.

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": {
      "slug": "<slug>"
    },
    "name": "get_polymarket_market"
  }
}

Input Schema

NameRequiredDescriptionDefault
slugYesPolymarket market slug (from the URL, or from search_polymarket_markets)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.1

TDQS

A4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, openWorldHint=true, idempotentHint=true, and destructiveHint=false, which together indicate a safe, idempotent read operation. The description adds a pricing note ($0.002 per call), which is useful behavioral context beyond what annotations provide. However, it doesn't mention potential network variability or failure modes, which with strong annotations is acceptable.

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 extremely concise with two sentences covering purpose, return data, and pricing. Every sentence adds value with no redundancy or fluff.

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 has only one parameter, no output schema, and strong annotations, the description adequately covers what the tool returns and costs. It misses mentioning whether prices are in USD or another unit, but the presence of sibling tools like get_crypto_price provides broader context. Overall sufficient for a simple lookup tool.

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% as the slug parameter is well-documented in the schema with a clear description. The description adds no further parameter details but is not required to; it simply clarifies the return fields. 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?

The description clearly states the tool retrieves 'Full detail for a single Polymarket market by slug' and lists the specific data returned (prices, volume, liquidity, resolution status). This distinguishes it from sibling tools like search_polymarket_markets which searches multiple markets.

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

Usage Guidelines4/5

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

The description explains to use a slug from the URL or from search_polymarket_markets, providing clear context for when to use this tool. It doesn't explicitly state when not to use it or name alternatives beyond the search tool, but the sibling list helps.

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