Skip to main content
Glama

Search markets

search_markets
Read-onlyIdempotent

Find Polymarket and Kalshi markets by words in the title, an exact market id, a Kalshi series, event or market ticker, or a market link. Returns each market's venue, id, title, open or closed status, Yes price and RulesWatch link, and a few recent rule edits on matching titles. Use it to find a market's venue and id from its name or link.

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": {
      "query": "<query>"
    },
    "name": "search_markets"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryYesOne or two distinctive title words ("Fed rate", "Senate Ohio"), a market id, a Kalshi ticker, or a Polymarket, Kalshi or RulesWatch market link.
venueNoOnly markets on this venue: pm (or polymarket) or kalshi. Leave out for both.

Output Schema

NameRequiredDescriptionDefault
noteNo
venueNo
changesNo
marketsNo
changes_noteNo
searched_forNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • removedOutput schema / properties / query
      Removed value: -{
      -  "type": [
      -    "string",
      -    "null"
      -  ]
      -}
    • addedOutput schema / properties / searched_for
      Added value: +{
      +  "type": [
      +    "string",
      +    "null"
      +  ]
      +}
  2. Changed4 schema fields changed
    • addedInput schema / properties / query / description
      Added value: +"One or two distinctive title words (\"Fed rate\", \"Senate Ohio\"), a market id, a Kalshi ticker, or a Polymarket, Kalshi or RulesWatch market link."
    • changedInput schema / properties / query / maxLength
      Previous value: -100New value: +300
    • addedInput schema / properties / venue
      Added value: +{
      +  "description": "Only markets on this venue: pm (or polymarket) or kalshi. Leave out for both.",
      +  "enum": [
      +    "pm",
      +    "polymarket",
      +    "kalshi"
      +  ],
      +  "maxLength": 10,
      +  "type": "string"
      +}
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "properties": {
      +    "changes": {
      +      "items": {
      +        "properties": {
      +          "id": {
      +            "type": [
      +              "integer",
      +              "null"
      +            ]
      +          },
      +          "kind_label": {
      +            "type": [
      +              "string",
      +              "null"
      +            ]
      +          },
      +          "market_title": {
      +            "type": [
      +              "string",
      +              "null"
      +            ]
      +          },
      +          "url": {
      +            "type": [
      +              "string",
      +              "null"
      +            ]
      +          }
      +        },
      +        "type": "object"
      +      },
      +      "type": "array"
      +    },
      +    "changes_note": {
      +      "type": [
      +        "string",
      +        "null"
      +      ]
      +    },
      +    "markets": {
      +      "items": {
      +        "properties": {
      +          "id": {
      +            "type": [
      +              "string",
      +              "null"
      +            ]
      +          },
      +          "status": {
      +            "type": [
      +              "string",
      +              "null"
      +            ]
      +          },
      +          "title": {
      +            "type": [
      +              "string",
      +              "null"
      +            ]
      +          },
      +          "url": {
      +            "type": [
      +              "string",
      +              "null"
      +            ]
      +          },
      +          "venue": {
      +            "type": [
      +              "string",
      +              "null"
      +            ]
      +          },
      +          "venue_code": {
      +            "type": [
      +              "string",
      +              "null"
      +            ]
      +          },
      +          "yes_price": {
      +            "type": [
      +              "number",
      +              "null"
      +            ]
      +          }
      +        },
      +        "type": "object"
      +      },
      +      "type": "array"
      +    },
      +    "note": {
      +      "type": [
      +        "string",
      +        "null"
      +      ]
      +    },
      +    "query": {
      +      "type": [
      +        "string",
      +        "null"
      +      ]
      +    },
      +    "venue": {
      +      "type": [
      +        "string",
      +        "null"
      +      ]
      +    }
      +  },
      +  "type": "object"
      +}
  3. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare read-only, idempotent, open-world, and non-destructive behavior. The description adds useful context by explaining that results include venue, id, title, status, Yes price, RulesWatch link, and a few recent rule edits on matching titles.

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 two tightly written sentences with the search scope front-loaded. The second sentence adds a clear usage cue without unnecessary detail or redundancy.

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?

The tool is not highly complex: two parameters, one required, with full schema coverage and an output schema. The description supplies enough context about search formats and result contents, though it could mention result limits or pagination if relevant.

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%, so the schema already documents both query and venue parameters. The description adds marginal meaning by mentioning Kalshi series and event or market ticker formats, but it largely repeats schema-level query examples and does not explain the venue parameter.

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 specific verb and resource: find markets by title words, market id, ticker, series, or link. It clearly explains what the tool searches and what it returns, though it does not explicitly distinguish itself from sibling tools like get_market.

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?

It gives a clear usage context: use it to find a market's venue and id from its name or link. It does not explicitly state when not to use it or name an alternative sibling tool, so it falls short of full alternatives guidance.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.