Skip to main content
Glama
predmarket-mcp

predmarket-mcp

get_market

Read-only

Retrieve the current quote and details for a single Kalshi or Polymarket prediction market using its ticker or slug to check live pricing and market info.

Instructions

Current quote and details for one market (Kalshi ticker or Polymarket slug).

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": {
      "venue": "<venue>",
      "market_id": "<market_id>"
    },
    "name": "get_market"
  }
}

Input Schema

NameRequiredDescriptionDefault
venueYes
market_idYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so safety and external-API exposure are covered. The description adds only the freshness signal in 'current quote', with no mention of rate limits, venue auth requirements, or what happens on an invalid ticker. Marginal added value over the structured fields.

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?

A single front-loaded sentence with the resource first and the identifier-format clarification parenthetically attached. No filler and no redundant restatement of the tool name.

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?

An output schema exists, so return values need no explanation, and the two-parameter surface is simple. The description covers the only ambiguity that matters, the venue-specific ID format; only error behavior for a bad ticker/slug is left unaddressed.

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 coverage is 0% and both fields are bare ('Venue', 'Market Id'), so the description carries the burden. It compensates by explaining that market_id is venue-dependent — a Kalshi ticker or a Polymarket slug — which the schema does not convey. The venue enum values are self-explanatory, so nothing further is needed there.

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?

States a specific verb ('get') and resource ('one market') plus what is returned ('current quote and details'), and disambiguates the identifier format per venue ('Kalshi ticker or Polymarket slug'). It implicitly contrasts with search_markets by scoping to a single market, but never names a sibling to steer away from.

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?

Usage is only implied: 'one market' suggests a single-entity lookup rather than a search, and the venue/identifier hint implies you must already know the ticker or slug. There is no explicit when-to-use versus get_orderbook, get_price_history, compare_venues, or search_markets, and no stated precondition or failure mode for an unknown identifier.

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