Skip to main content
Glama

Scanverity Public Market Discovery

Find prediction markets for a topic or question

scanverity_search_markets
Read-onlyIdempotent

Use this account-free, read-only search when a user asks which prediction markets cover a topic, forecast, event deadline or settlement question. Search short keywords and show exact contracts, IDs, source links, deadlines and any verified outcomes. Results are a bounded identity search, not a resolution assessment, live odds, profit forecast or guarantee that absent markets do not exist. Ask the user to select one contract; for deeper written research use scanverity_offers and its EUR100 quote route. This public connector cannot request a paid report or take payment.

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": "scanverity_search_markets"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum contracts on this page, default 5.
queryYesA short topic or keyword from the user question; omit personal information. Prefer English market wording. Do not pass a full URL or a long conversational prompt.
cursorNoExact next_cursor from the previous page with the same query, dates and limit. An empty truncated page is not proof of absence.
end_date_toNoLatest scheduled end date, YYYY-MM-DD; set when the user specifies a horizon.
end_date_fromNoEarliest scheduled end date, YYYY-MM-DD; defaults to today UTC. Only active rows from the available identity source.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=true. The description adds meaningful context beyond that: it is account-free, bounded rather than exhaustive, not a resolution/odds/forecast assessment, and cannot initiate payment. The payment/auth constraints are genuinely additive, though return format and pagination specifics remain thin.

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?

Front-loaded with the trigger condition in the opening clause and organized as trigger, output, caveats, and routing to the sibling. Five dense sentences with no obvious filler, though it runs slightly long.

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?

No output schema exists, so the description usefully enumerates what results contain (exact contracts, source links, deadlines, verified outcomes) and clarifies scope limits. Covers the essentials for a search tool; only minor gaps around pagination/return structure remain.

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 description coverage is 100%, so every parameter is already documented in the schema. The description reinforces query intent ('search short keywords') and implies bounded paging but adds no syntax or format detail beyond the schema. Baseline 3 is correct when the schema carries the parameter burden.

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?

States a specific verb and resource (search prediction markets) plus the scope of what it returns (contracts, source links, deadlines, verified outcomes). It explicitly distinguishes itself from its sibling scanverity_offers by reserving that tool for 'deeper written research.' An agent can tell the two apart without opening either schema.

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

Usage Guidelines5/5

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

Opens with a precise trigger ('when a user asks which prediction markets cover a topic, forecast, event deadline or settlement question'), names the alternative for deeper research (scanverity_offers with its EUR100 quote route), and states a when-not boundary (cannot request a paid report or take payment). Explicit when, when-not, and alternative coverage.

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