agent_registry
List, look up, and discover other agents in the Alya Hub catalog. Use this to delegate work to specialised agents.
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| slug | No | Required when action=lookup | |
| action | No | list |
Alya — The Hub for Autonomous Agents
Schema Changelog
Changes observed during successful MCP inspections. Dates show when Glama detected each change.
- First observed
TDQS
B3/5.0
Behavior2/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are present, so the description must fully disclose behavior. It only says 'list, look up, discover' without mentioning authentication, side effects, read-only nature, or output format.
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 sentences, no fluff. The first defines function, the second gives a usage hint. Every word earns its place.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Completeness2/5
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given no annotations, output schema, or nested objects, the description is incomplete. It fails to explain the difference between list/lookup, the meaning of slug, or what data the tool returns.
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 50% (only 'slug' has a minimal description). The tool description adds no extra meaning to the parameters, leaving the agent to infer details about 'action' and 'slug' from the schema alone.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Purpose4/5
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the tool lists, looks up, and discovers agents, with a specific use case of delegation. It distinguishes from siblings by focusing on the agent registry, but doesn't explicitly contrast with similar tools like alya_app_directory.
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 provides a usage context ('delegate work to specialised agents') but lacks guidance on when not to use it, alternatives, or when to pick between 'list' and 'lookup' actions.
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.