polymarket_edge
PREMIUM ($0.50/call). Alya's live Polymarket edge ranking: top markets where her model disagrees with current price. Built on 6+ months of in-house arb history.
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| limit | No |
Alya Hub
TDQS
B3.1/5.0
Behavior3/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
The description discloses the cost ($0.50/call) and the data source (6+ months of in-house arb history), which are important behavioral traits. However, with no annotations, it fails to mention read-only nature, rate limits, or data update frequency, leaving the agent partially uninformed.
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?
The description is concise with two sentences that front-load the premium warning. Each sentence adds value: cost, functionality, and historical basis. Minor improvement could be a clearer structure.
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 1-parameter tool with no output schema or annotations, the description provides essential context (premium cost, live ranking) but omits what the output contains (e.g., market names, percentages). It is adequate but not fully complete.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Parameters1/5
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The schema has 0% description coverage and the description does not mention the single parameter 'limit'. The agent receives no guidance on how to control the number of results or what the default behavior is beyond the schema's default value.
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 provides a live ranking of Polymarket markets where the model's prediction disagrees with the current price, using the specific verb 'ranking' and resource 'top markets'. It differentiates from sibling tools like 'polymarket_signals' and 'polymarket_top_traders' by focusing on model disagreement.
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 alternatives like 'polymarket_signals' or 'polymarket_categorize'. There is no mention of prerequisites, limitations, or when not to use it.
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.
TDQS
B3.4/5.0
Disambiguation4/5
Most tools have distinct purposes and clear descriptions, but there is some potential confusion among the four Polymarket-related tools (categorize, edge, signals, top_traders) and among the multiple 'alya_' prefixed tools that query different data sources.
Naming Consistency3/5
Naming patterns are mixed: some tools use 'alya_' prefix, others use action-based names like 'batch_calibrate' or 'image_gen', and YouTube tools all start with 'youtube_'. The inconsistency in prefixes and verb styles makes the set less predictable.
Tool Count2/5
32 tools is high for an MCP server, and they span a wide, unrelated set of domains (Polymarket, YouTube, gemology, weather, earthquakes, health, celebrity, etc.), making the surface feel bloated and unfocused.
Completeness2/5
Each domain has incomplete coverage: Polymarket lacks trade execution, YouTube automation depends on external OAuth, health tools only offer diagnosis and drug interactions without follow-up, and other domains have minimal tooling. The server feels like a collection of one-off features rather than a coherent surface.