Skip to main content
Glama

Manifold

by markets.manifold.api
OverviewDiscussionsAdmin

Search Markets

search-markets

Search for prediction markets with optional filters

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
sortNoSort order for market search (default: score). Do not use /markets sort values here.
termYesSearch query
limitNoMax number of results (default: 100)
offsetNoOffset for pagination (default: 0)
creatorIdNoOptional. Creator (user) ID to filter by
contractTypeNoMarket/question type filter (default: ALL). Use contractType, not outcomeType.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / contractType / enum
      Previous value: -[
-  "ALL",
-  "BINARY",
-  "MULTIPLE_CHOICE",
-  "DEPENDENT_MULTIPLE_CHOICE",
-  "INDEPENDENT_MULTIPLE_CHOICE",
-  "FREE_RESPONSE",
-  "PSEUDO_NUMERIC",
-  "BOUNTIED_QUESTION",
-  "STONK",
-  "POLL",
-  "NUMBER",
-  "MULTI_NUMERIC",
-  "DATE"
-]New value: +[
+  "ALL",
+  "BINARY",
+  "MULTIPLE_CHOICE",
+  "DEPENDENT_MULTIPLE_CHOICE",
+  "INDEPENDENT_MULTIPLE_CHOICE",
+  "FREE_RESPONSE",
+  "PSEUDO_NUMERIC",
+  "BOUNTIED_QUESTION",
+  "STONK",
+  "POLL",
+  "NUMBER",
+  "MULTI_NUMERIC",
+  "DATE",
+  "PERP"
+]
  2. Changed6 schema fields changed
    • addedInput schema / additionalProperties
      Added value: +false
    • changedInput schema / properties / contractType / description
      Previous value: -"Question type (default: ALL)"New value: +"Market/question type filter (default: ALL). Use contractType, not outcomeType."
    • changedInput schema / properties / contractType / enum
      Previous value: -[
-  "ALL",
-  "BINARY",
-  "MULTIPLE_CHOICE",
-  "DEPENDENT_MULTIPLE_CHOICE",
-  "INDEPENDENT_MULTIPLE_CHOICE",
-  "POLL",
-  "MULTI_NUMERIC",
-  "DATE"
-]New value: +[
+  "ALL",
+  "BINARY",
+  "MULTIPLE_CHOICE",
+  "DEPENDENT_MULTIPLE_CHOICE",
+  "INDEPENDENT_MULTIPLE_CHOICE",
+  "FREE_RESPONSE",
+  "PSEUDO_NUMERIC",
+  "BOUNTIED_QUESTION",
+  "STONK",
+  "POLL",
+  "NUMBER",
+  "MULTI_NUMERIC",
+  "DATE"
+]
    • removedInput schema / properties / filter
      Removed value: -{
-  "description": "Filter by question state. Resolved means the event has happened. (default: all)",
-  "enum": [
-    "open",
-    "resolved",
-    "all"
-  ],
-  "type": "string"
-}
    • changedInput schema / properties / sort / description
      Previous value: -"Sort order (default: score)"New value: +"Sort order for market search (default: score). Do not use /markets sort values here."
    • changedInput schema / properties / sort / enum
      Previous value: -[
-  "newest",
-  "score",
-  "liquidity"
-]New value: +[
+  "newest",
+  "score"
+]
  3. First observed

TDQS

B3.2/5.0
Behavior2/5

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

No annotations are present, and the description does not disclose any behavioral traits such as search algorithm, result format, or pagination behavior. It only states the purpose, leaving the agent without information about what happens when the tool is invoked.

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 one concise sentence that states the core purpose without unnecessary words, making it well-structured and front-loaded.

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?

Despite having a fully described schema, the description does not mention what the tool returns, how pagination works, or any behavioral limitations. Without an output schema or annotations, the agent is left with incomplete context about the search operation.

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 input schema fully documents all six parameters, so the description does not need to add semantics. It adds no extra meaning beyond saying 'optional filters', so the baseline of 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's function with a specific verb ('search') and resource ('prediction markets'), and mentions optional filters, distinguishing it from sibling tools like get-market which retrieves a single market.

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?

No guidance is provided on when to use this tool versus get-market or search-users. The description only states what it does, not when it should be chosen, so there is no usage direction.

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

All Manifold toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources