PolyDesk

get_prices

Retrieve current prices for multiple Polymarket markets by ID to refresh watchlists or check positions.

Instructions

Get current prices for one or more markets by ID. Use this to refresh watchlist or check positions.

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": {
      "market_ids": "<market_ids>"
    },
    "name": "get_prices"
  }
}

Input Schema

Name	Required	Description	Default
`market_ids`	Yes	Array of Polymarket market IDs

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Aug 30, 2026

TDQS

A3.8/5.0

Behavior3/5

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

With no annotations provided, the description must carry the behavioral disclosure burden. It implies a safe read-only operation ('get current prices') but doesn't mention how errors are handled, whether the data is live vs. cached, or what constitutes a 'current price.' This is adequate for a simple price fetch but not deeply transparent.

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?

Two sentences with no wasted words. The purpose is front-loaded and the usage guidance is immediately actionable. It earns its place.

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?

For a tool with one well-documented parameter and no output schema, the description is sufficient to call it correctly. It doesn't describe the response shape or error behavior, but those are not critical for a straightforward price query given the low complexity. Minor gaps remain, but overall completeness is strong.

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?

The schema has 100% coverage for the single parameter 'market_ids,' including a clear description. The description adds no extra parameter meaning beyond echoing 'by ID' and 'markets.' Baseline 3 is appropriate when the schema already documents the parameter well.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a clear verb and resource: 'Get current prices for one or more markets by ID.' This is specific and actionable. It doesn't explicitly distinguish from siblings like get_market or search_markets, but the purpose is unambiguous on its own.

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 provides clear context for when to use the tool: 'Use this to refresh watchlist or check positions.' It gives practical scenarios but does not explicitly mention alternatives or exclusion cases, so it falls short of the highest bar.

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