alya_ask
Ask Alya - the operator agent. Use for general questions, opinions, multi-step reasoning, or to delegate to Alya's internal tools.
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| lang | No | ||
| question | Yes |
Alya — The Hub for Autonomous Agents
Schema Changelog
Changes observed during successful MCP inspections. Dates show when Glama detected each change.
- First observed
TDQS
A3.9/5.0
Behavior3/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description hints at delegation and multi-step reasoning but lacks specifics on limitations, side effects, or autonomy; partially informative but incomplete.
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 two concise sentences, front-loaded with purpose and usage, with no superfluous content.
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 the complexity of a general agent tool, the description covers delegation and reasoning but omits details about output format or potential delays; mostly complete.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Parameters2/5
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema coverage is 0% and the description does not explain the 'question' or 'lang' parameters, adding no meaning beyond the schema itself.
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 is a general-purpose agent for questions, opinions, reasoning, and delegation, distinguishing it from sibling tools that are task-specific.
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?
The description explicitly says 'Use for general questions... or to delegate' which implies using sibling tools for specific tasks, but does not explicitly list when not to use it or name alternatives.
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
A3.5/5.0
Disambiguation4/5
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.
Naming Consistency3/5
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.
Tool Count3/5
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.
Completeness4/5
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.