Skip to main content
Glama

Search prediction markets

prediction_search

Search prediction markets by keyword to find the market for a specific event.

Instructions

Search prediction markets by keyword. Use to find the market for a specific event.

PAID TOOL: up to $0.005 USDC per call (x402 on Base). Paid automatically from your configured wallet.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
queryYesSearch text.
Behavior3/5

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

No annotations provided, so description must carry burden. It discloses it's a paid tool with cost ($0.005 USDC per call), which is a behavioral trait. However, it lacks details like result format, error handling, or rate limits.

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?

Two sentences plus a cost notice, no wasted words. Information is front-loaded with purpose. Could be slightly more structured but efficient.

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

Completeness3/5

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

For a simple one-parameter search tool, it explains the purpose and cost. However, it doesn't describe the output (e.g., list of markets) or ranking, which would be helpful for completeness.

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% with parameter 'query' described as 'Search text.' The description adds 'by keyword' which is similar. Baseline 3 as schema already covers meaning.

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?

Clearly states it searches prediction markets by keyword to find a market for a specific event. The verb 'search' and resource 'prediction markets' are specific, and it distinguishes from siblings like prediction_history or prediction_markets.

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?

Explicitly says 'Use to find the market for a specific event,' providing clear context. Does not explicitly state when not to use or mention alternatives, but the context is sufficient.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/lucle87/boo-x402-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server