Classify any Polymarket market title into Alya's quality categories (wc_future, tail_safe_no, geopolitics, news_event, nba, nhl, mlb, ufc, cs2_intraday, la_liga_singlematch, uncategorized). Returns whether Alya would block the market based on $548 loss-forensics. Use this to pre-screen any market before placing real money.
| Name | Required | Description | Default |
|---|---|---|---|
| titles | Yes | 1..50 market titles to categorize |
Changes observed during successful MCP inspections. Dates show when Glama detected each change.
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description carries full burden. It discloses the output includes a blocking decision based on loss-forensics, but lacks details on how categorization works, output format, or potential side effects.
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?
The description is two succinct and front-loaded sentences that convey the main action, categories, and purpose without unnecessary 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?
Given no output schema, the description partially covers return value (block decision and categories) but omits exact return format, error handling, and limitations. Adequate but not fully complete.
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?
Schema coverage is 100% with a brief description of the titles parameter. The tool description adds meaningful context by listing the specific categories, which helps the agent understand valid inputs beyond the schema.
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?
The description clearly states the tool classifies Polymarket market titles into specific quality categories and returns a blocking decision. It distinguishes the action but does not differentiate from sibling tools like polymarket_edge or polymarket_signals.
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?
The description advises using the tool to pre-screen before placing real money, providing a clear use case. However, it does not specify when not to use it or suggest alternatives among sibling tools.
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 have distinct purposes, with clear separation across domains like finance, healthcare, gems, and YouTube. Some overlap exists between 'alya_ask' and 'web_search' for general queries, but descriptions help differentiate.
Tools use snake_case consistently, but there is inconsistency in the use of the 'alya_' prefix – some tools have it, others don't (e.g., 'batch_calibrate', 'web_search'). Related tools like 'calibrate_decision' and 'batch_calibrate' are not grouped by prefix.
With 32 tools, the count is high but arguably appropriate for a 'hub' serving multiple domains. However, it feels slightly heavy and could be streamlined, especially given overlapping query capabilities.
The tool surface covers major workflows (e.g., YouTube content creation, Polymarket trading, gem appraisal, healthcare checks) with few obvious dead ends. Minor gaps exist, such as lack of a tool to place Polymarket bets directly or edit gem entries.