List all paid endpoints exposed by this MCP server with their prices and live status. Free — no wallet required. Use this first to discover what tools are available.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations provided, so description carries full burden. While the read-only nature is implied for a list operation, it does not explicitly state safety or lack of side effects. Mentions 'Free' but does not cover rate limits or other behavioral traits.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Two sentences, front-loaded with action and result. Every sentence adds value: first defines action, second gives usage hint. No wasted words.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Describes return content (prices, live status) but lacks detail on format or potential filtering. Adequate for a simple list tool with no output schema, though could be more precise.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
No parameters in schema (100% coverage), so baseline of 4 applies. Description adds no parameter detail beyond schema, which is expected.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
Clearly states the tool lists all paid endpoints with prices and live status. Uses specific verb 'list' and resource 'paid endpoints', distinguishing it from siblings like pricing_info which may focus on pricing details.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
Explicitly says 'Use this first to discover what tools are available' and 'Free — no wallet required', providing clear ordering and prerequisite guidance. Does not explicitly contrast with alternatives but offers strong usage context.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
Most tools occupy distinct roles (install, usage stats, wallet setup), but list_endpoints and pricing_info overlap substantially: both report paid endpoints and prices, even though one emphasizes live status and the other detailed fees/payment networks. Descriptions help separate them, but an agent could still pick the wrong one for a pricing question.
Names are uniformly snake_case and readable, but the pattern is mixed: install_snippets and list_endpoints use verb_noun, while pricing_info, usage_stats, and wallet_helper use noun-based names. This is a readable mixed convention rather than a chaotic one.
Five tools is a reasonable number for a small server, but for a product called 'Prediction Market Data for AI Agents' the set is oddly scoped: everything is onboarding/pricing/usage meta-tools rather than data tools. The count is not excessive, but it feels thin for the apparent market-data purpose.
The server promises prediction market data, yet none of the five tools retrieves markets, odds, prices, positions, or any actual market data. Even if the free helper tools are complete, the core data surface is entirely absent, leaving agents with no way to fulfill the server's stated purpose.