meridian-edge-mcpofficial
A
licenseA
qualityD
maintenanceProvides AI assistants with real-time prediction market consensus data, including probabilities, opportunities, signals, and settlements.
5
MIT
Prediction Markets
Server Details
Prediction market data and crowd-sourced probability forecasts
- Status
- Healthy
- Last Tested
- Transport
- Streamable HTTP
- URL
Glama MCP Gateway
Connect through Glama MCP Gateway for full control over tool access and complete visibility into every call.
MCP client
Glama
MCP server
Full call logging
Every tool call is logged with complete inputs and outputs, so you can debug issues and audit what your agents are doing.
Tool access control
Enable or disable individual tools per connector, so you decide what your agents can and cannot do.
Managed credentials
Glama handles OAuth flows, token storage, and automatic rotation, so credentials never expire on your clients.
Usage analytics
See which tools your agents call, how often, and when, so you can understand usage patterns and catch anomalies.
100% free. Your data is private.
Tool Definition Quality
A4/5.0
Tool DescriptionsA
Average 3.8/5 across 3 of 3 tools scored.
Server CoherenceA
Disambiguation5/5
Each tool has a clearly distinct purpose: browsing markets with filters, getting detailed information on a specific market, and fetching trending markets. There is no functional overlap.
Naming Consistency5/5
All tool names follow a consistent verb_noun pattern in snake_case: browse_prediction_markets, get_market_details, get_trending_predictions.
Tool Count5/5
Three tools is appropriate for a focused server covering browsing, details, and trending. The scope is well-defined without being too sparse or bloated.
Completeness4/5
The set covers the core information retrieval needs: discover, examine, and see trends. A minor gap is historical data or outcome timelines, but for a lightweight server this is reasonable.
Available Tools
3 toolsbrowse_prediction_marketsAInspect
Browse prediction markets from Polymarket and Manifold. Filter by category (crypto, politics, sports, economics, science, entertainment, pop-culture) or search by keyword.
ParametersJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| q | No | Keyword search | |
| tag | No | Category filter (crypto, politics, sports, economics, science, entertainment, pop-culture) | |
| limit | No | Number of results (default 20, max 50) | |
| source | No | polymarket, manifold, or all (default: all) | all |
Tool Definition Quality
A3.7/5.0
Behavior2/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries full burden. It mentions 'browse' which implies a read operation, but does not explicitly state read-only behavior, rate limits, response structure, or pagination. Basic disclosure only.
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?
Two clear, front-loaded sentences with no wasted words. The main action and key filters are stated first.
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?
Given 4 optional parameters, no output schema, and no annotations, the description provides a reasonable overview but lacks details on response format, pagination, or usage constraints. Adequate for a browsing tool, but gaps remain.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Parameters4/5
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 100%, baseline 3. The description adds value by listing the possible categories for the tag parameter and explaining the source parameter options (polymarket, manifold, all). This contextualizes the parameters beyond the schema.
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 verb 'browse', the resource 'prediction markets', and the specific sources 'Polymarket and Manifold'. It also mentions filtering by category or keyword, which distinguishes it from sibling tools that likely focus on details or trends.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Usage Guidelines3/5
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description implies usage for browsing/filtering but does not explicitly state when to use this tool versus alternatives like get_market_details or get_trending_predictions. No exclusion criteria or prerequisites are given.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
get_market_detailsAInspect
Get detailed information for a specific prediction market including prices, outcomes, and trading volume.
ParametersJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| id | No | Market ID or condition_id. If not provided, returns the highest volume active market. | |
| source | No | polymarket or manifold (default: polymarket) | polymarket |
Tool Definition Quality
A4.2/5.0
Behavior4/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries full burden. It discloses that omitting the id returns the highest volume active market, which is useful behavioral context. However, it does not explicitly state that the operation is safe/read-only, though it is implied.
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 a single, well-structured sentence with no redundant information. All words earn their place, and key details are front-loaded.
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?
Given two parameters and no output schema or annotations, the description covers what the tool returns (prices, outcomes, volume) and the default behavior for the id parameter. It could be improved by explicitly stating it is a read-only operation, but overall it is sufficient.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Parameters4/5
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema coverage is 100%, baseline 3. The description adds value by explaining that omitting the id parameter defaults to the highest volume active market. For the source parameter, it restates the default and allowed values already in the schema, providing reinforcement.
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 verb 'Get' and the resource 'detailed information for a specific prediction market', including examples of data (prices, outcomes, trading volume). It effectively distinguishes from sibling tools like browse_prediction_markets and get_trending_predictions, which focus on browsing or trending rather than specific market details.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Usage Guidelines3/5
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description implies usage for retrieving details on a specific market, but does not explicitly state when to use it versus siblings or provide when-not-to-use guidance. The sibling tool names are only in context signals, not mentioned in the description.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
get_trending_predictionsAInspect
Get what the prediction markets are betting on right now. Fetches top markets by volume/liquidity.
ParametersJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| limit | No | Number of results (default 10, max 50) | |
| source | No | polymarket, manifold, or all (default: all) | all |
Tool Definition Quality
A3.6/5.0
Behavior2/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations provided. Description lacks disclosure of side effects, permissions, rate limits, or data freshness. 'Fetches' implies read-only but not explicit. Needs more behavioral context.
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?
Two concise sentences: first states main purpose, second adds detail. No fluff, front-loaded. Every sentence adds value.
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?
Simple tool without output schema. Description explains what is fetched and why. Lacks explicit mention of return format but sufficient for typical usage. Well-contextualized among siblings.
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 has 100% coverage on both parameters (limit, source). Description adds minor context ('top markets by volume/liquidity') but doesn't significantly enhance meaning beyond schema. Baseline 3.
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 verb 'get' and resource 'prediction markets', specifying 'top markets by volume/liquidity'. Distinguishes from siblings: browse_prediction_markets (general) and get_market_details (specific).
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Usage Guidelines3/5
Does the description explain when to use this tool, when not to, or what alternatives exist?
Implicitly suggests use for current trending markets ('right now', 'top by volume/liquidity'), but no explicit when-to-use or alternatives compared to siblings.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Claim this connector by publishing a /.well-known/glama.json file on your server's domain with the following structure:
{
"$schema": "https://glama.ai/mcp/schemas/connector.json",
"maintainers": [{ "email": "your-email@example.com" }]
}The email address must match the email associated with your Glama account. Once published, Glama will automatically detect and verify the file within a few minutes.
Control your server's listing on Glama, including description and metadata
Access analytics and receive server usage reports
Get monitoring and health status updates for your server
Feature your server to boost visibility and reach more users
For users:
Full audit trail – every tool call is logged with inputs and outputs for compliance and debugging
Granular tool control – enable or disable individual tools per connector to limit what your AI agents can do
Centralized credential management – store and rotate API keys and OAuth tokens in one place
Change alerts – get notified when a connector changes its schema, adds or removes tools, or updates tool definitions, so nothing breaks silently
For server owners:
Proven adoption – public usage metrics on your listing show real-world traction and build trust with prospective users
Tool-level analytics – see which tools are being used most, helping you prioritize development and documentation
Direct user feedback – users can report issues and suggest improvements through the listing, giving you a channel you would not have otherwise
The connector status is unhealthy when Glama is unable to successfully connect to the server. This can happen for several reasons:
The server is experiencing an outage
The URL of the server is wrong
Credentials required to access the server are missing or invalid
If you are the owner of this MCP connector and would like to make modifications to the listing, including providing test credentials for accessing the server, please contact support@glama.ai.
Discussions
No comments yet. Be the first to start the discussion!
Related MCP Servers
- FlicenseNot gradedqualityCmaintenanceLive analytics at the edge across prediction markets
- AlicenseAqualityDmaintenancePrediction market probability oracle for AI agents. 26 tools across 500+ live markets from Kalshi and Polymarket. Cross-source arbitrage detection, structured TPF signals, Kelly Criterion sizing, agent performance tracking, and webhook alerts.9611MIT
- AlicenseAqualityDmaintenanceReal-time prediction market consensus data for AI agents. Aggregates probabilities from 27,000+ markets across politics, sports, and economics with 14-second updates. Tools: get_markets, get_consensus, get_movers, get_divergences, search_markets.5MIT