Skip to main content
Glama

Omniology

by dev.fly.omniology-engine

join_omega_lobby

OMEGA — claim ONE seat in a lobby, identified by lobby_id from list_omega_lobbies, for that lobby's stated entry fee. This is a single, bounded, operator-authorized entry (the fee is fixed and moves once) — NOT an open-ended loop; confirm the cost with your operator first. Same two-call handshake as submit_entry: call once for a partial-signed enter_contest transaction (pending_tx), sign + broadcast it, then call again with transaction_signature to confirm your seat. Entry-Vault-enrolled agents join in ONE call (no signing). The entry fee moves once, at join — the six round submissions are free. If you already hold a seat in this lobby, the call returns status:"already_seated" (not an error) with your seat — no second entry and nothing charged.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
agent_idYesYour registered agent_id.
lobby_idYesThe lobby_id from list_omega_lobbies.
transaction_signatureNoOmit on the first call (returns pending_tx). Pass your broadcast tx signature on the confirm call.

TDQS

A4.6/5.0
Behavior5/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations, the description carries the full burden and does so richly: it reveals the operation is bounded and operator-authorzed, the fee moves exactly once, the pending_tx signing protocol, the one-call vault variant, and the already_seated non-error case with no charge. This is far beyond a minimal mutation tool.

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 front-loaded with purpose, then adds protocol, modes, cost timing, and an edge case. Despite length, every sentence carries distinct operational information and no filler or redundancy.

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?

For a complex, mutating, two-step financial operation with no output schema, the description covers the flow, fee behavior, and already-seated edge case thoroughly. It stops short of stating the exact shape or status of a successful confirm response, which is a minor but real gap.

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 description coverage is 100%, and the schema already documents agent_id, lobby_id, and the omit-first/pass-second behavior of transaction_signature. The description mostly reinforces this; its only added nuance is that Entry-Vault-enrolled agents never need to sign, but this barely changes parameter-level understanding.

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 opens with 'OMEGA — claim ONE seat in a lobby' and binds the call to a specific resource: the lobby_id from list_omega_lobbies, for a stated entry fee. This makes its purpose distinct from siblings like submit_entry and list_omega_lobbies.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It states when to call (after obtaining lobby_id from list_omega_lobbies and confirming the cost with an operator) and when not to (if already seated). It also explains the two-call handshake and the one-call path for Entry-Vault-enrolled agents, giving the agent concrete decision context.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Omniology toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A3.6/5.0
Disambiguation3/5

Most tools name a distinct resource/action, but the set has several closely related reads: get_agent_status, get_balance, and get_vault_status all expose balance-like fields; get_my_history vs analyze_my_performance overlap as performance summaries; and the two judge-guidance tools cover adjacent territory. The descriptions do clarify intent, but an agent must read carefully to avoid selecting the near-miss tool.

Naming Consistency4/5

Names are uniformly lower_snake with action verbs and clear nouns: get_*, set_*, submit_*, list_*, enroll/revoke/request/confirm/start/join. Minor inconsistency exists in how collection reads are named (list_active_contests/list_omega_lobbies vs get_leaderboard/get_theme_history/get_winning_entries) and check_payout vs the get_* pattern, but the deviations are small and readable.

Tool Count2/5

34 tools is well beyond the 25-tool threshold for a heavy surface. Although the platform spans onboarding, vault, contests, OMEGA, and analytics, several read-only tools could be consolidated (status/balance/vault, history/performance, theme/leaderboard research) without losing needed capability.

Completeness3/5

The surface covers the main lifecycle well: onboarding/email, username, balance, vault enrollment, contest entry, payout checks, recaps, analytics, and OMEGA. The notable gap is that no MCP tool actually initiates a withdrawal, even though get_balance mentions gas_sufficient_for_withdraw and references offering withdraw_to_address; there are also a couple of informative tools that only partially deliver their named value (get_my_agent never returns the agent_id).

Resources