Skip to main content
Glama

search_polymarket_markets

Search Polymarket markets by question text.

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_polymarket_markets"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
queryYesSearch text

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.7/5.0
Behavior2/5

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

No annotations are supplied, so the description bears the full burden: it never states that this is a read-only operation, whether results are ordered by relevance, whether matching is substring or fuzzy, or what happens if no markets match. For a search tool with zero annotation coverage, that leaves the agent guessing about core behavior.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single front-loaded sentence with no filler, which is the right shape for a simple search tool. The brevity is efficient rather than padded, though it shades into under-specification elsewhere.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The tool is simple (two parameters, no nesting, no output schema), so the description need not explain return values, but it still omits the limit parameter's meaning and any notion of result ordering or empty-result behavior. Given no annotations at all, one sentence is not enough for an agent to call this confidently.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is only 50%: the query parameter is documented ("Search text") while limit has no description anywhere. The description's phrase "by question text" adds essentially nothing beyond the existing schema text for query and does not compensate for the undocumented limit parameter, such as its default or maximum.

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 names a specific verb and resource ("Search Polymarket markets") and adds the search key ("by question text"), which distinguishes it from a plain listing. It does not, however, name the obvious sibling list_polymarket_markets or explain how the two differ, so the agent must infer the distinction.

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

Usage Guidelines2/5

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

There is no statement of when to use this versus list_polymarket_markets, get_polymarket_market, or rank_polymarket_markets, and no exclusions or prerequisites. The only usage signal is the implied "use text search when you have a keyword," which is left entirely to inference.

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.

Resources