Skip to main content
Glama

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
ROTIFER_CLOUD_ANON_KEYNoCustom Rotifer Cloud API anonymous key.
ROTIFER_CLOUD_ENDPOINTNoCustom Rotifer Cloud API endpoint (e.g., a Supabase instance URL).

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{}
prompts
{}
resources
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
search_genesC

Search the Rotifer Gene ecosystem. Returns a list of Genes matching the query, filterable by domain and fidelity.

get_gene_detailA

Get detailed information about a specific Gene by its ID or content_hash, including phenotype, fitness, and metadata. At least one of gene_id or content_hash must be provided.

get_arena_rankingsA

Get Arena rankings for a domain. Each row carries a tier — verified (measured in a sandbox, with enough independent callers to stand), under_evaluation (measured, not yet corroborated), not_evaluated (disqualified, or a number that was estimated rather than measured) — and rank is null wherever the tier grants no rank. Prefer verified when picking a Gene for a capability; an estimated or disqualified number is not a measurement of anything. Also returns F(g) before and after the fidelity discount, safety, success_rate, latency, resource_efficiency, sample size and unique callers.

compare_genesA

Compare two or more Genes by their F(g) fitness metrics. Returns side-by-side fitness breakdown.

get_gene_statsB

Get download statistics for a Gene, broken down by time period (total, last 7 days, 30 days, 90 days).

get_leaderboardB

Get the creator reputation leaderboard. Shows top creators ranked by reputation score, including their published gene count, total downloads, and arena wins.

get_developer_profileB

Get a creator's public profile and reputation data by username.

list_local_genesA

List Genes installed in the local project workspace. Scans the genes/ directory for phenotype.json files and returns metadata, compile status, and cloud origin for each Gene.

list_local_agentsA

List Agents registered in the local project workspace. Returns each Agent's name, state, genome composition, strategy, and reputation. Agents are local constructs that compose multiple Genes into pipelines.

install_geneA

Install a Gene from the Rotifer Cloud Registry into the local project. Downloads phenotype, metadata, and the compiled WASM artifact (verified against declared size and sha256) when the gene has one. Requires a valid gene_id from search_genes or get_gene_detail.

rollback_geneA

Undo the last overwrite of a locally installed Gene, restoring the copy that install_gene replaced. Call without gene_name to list what can currently be rolled back. A rollback consumes its snapshot: it undoes one step, not a history.

arena_submitA

Measure a local Gene in the sandbox and submit the measured result to the Arena. Requires authentication (rotifer login) and a Gene that exists locally — use list_local_genes to see them, install_gene to fetch one. The fitness scores are produced by running the Gene, not supplied by the caller: passing fitness_value, safety_score, success_rate, latency_score or resource_efficiency is refused. Runs rotifer arena submit <gene> --cloud.

create_agentA

Create a new Agent by composing one or more local Genes. The Agent is saved to .rotifer/agents/ in the project. Genes must exist locally (wrap them first with wrap_gene).

agent_runA

Run a local Agent by name. Executes via the Rotifer CLI (rotifer agent run ). The Agent must exist in .rotifer/agents/. Returns stdout/stderr from the execution.

compile_geneA

Compile a local Gene to WASM via the Rotifer CLI (rotifer compile). The Gene must exist in the local genes/ directory. Returns compilation output.

doctorA

Check the local TypeScript→WASM toolchain (esbuild / javy) and report what is missing or misconfigured. Read-only: inspects the environment and changes nothing. Use this when compile_gene fails — a missing or broken toolchain is the most common cause.

run_geneA

Execute a local Gene via the Rotifer CLI (rotifer run). The Gene must exist in the local genes/ directory. Returns execution output.

init_geneB

Initialize a new Rotifer Gene project. Creates a directory with phenotype.json template and starter files. Supports Wrapped, Hybrid, and Native fidelity types.

scan_genesB

Scan source files for candidate gene functions or local SKILL.md files that can be wrapped as Genes. Returns discovered candidates with metadata.

wrap_geneB

Wrap a function or SKILL.md as a Rotifer Gene. Generates phenotype.json from the source. The target must exist in the project.

test_geneB

Test a Gene in the sandbox. Validates phenotype schema, runs input/output tests, and checks compilation.

publish_geneA

Publish a Gene to Rotifer Cloud Registry (default destination since v0.8.8). Calling this tool = explicit publish consent. Requires authentication (use login tool first). Validates with V(g) security scan (Grade >= B required), uploads, and optionally submits to Arena. Either gene_name or all=true must be provided.

list_gene_versionsA

List the version history chain of a Gene by creator and name. Returns all published versions in chronological order with changelog entries and previous_version_id links.

get_mcp_statsA

Get MCP Server call analytics for a given time period. Returns total calls, success rate, average latency, top tools, and top genes. Requires authentication.

auth_statusA

Check current authentication status. Returns whether the user is logged in, their username, provider, and how many minutes until the token expires.

loginA

Log in to Rotifer Cloud. Opens the browser for OAuth authorization (GitHub or GitLab). After the user authorizes in the browser, credentials are saved locally. This must be done before using arena_submit or publish_gene.

logoutA

Log out from Rotifer Cloud. Clears locally saved credentials.

get_gene_reputationB

Get detailed reputation breakdown for a Gene (Arena, Usage, Stability scores).

get_my_reputationB

Get the current logged-in creator's reputation and stats. Requires authentication.

suggest_domainC

Suggest top matching domains from the domain registry based on a description.

vg_scanB

V(g) security scan — static analysis for Gene/Skill code safety. Returns a grade (A/B/C/D/?) and per-finding details with severity, file, line, and snippet.

Prompts

Interactive templates invoked by user choice

NameDescription
rotifer-helloInteractive agent creation — choose a template and build an agent in seconds
rotifer-guideUnderstand Rotifer Protocol — core concepts, Gene model, and how agents work
rotifer-architectDesign an Agent — select genes, choose composition, define pipeline
rotifer-challengeArena evaluation — submit a gene, compare with competitors, understand fitness scoring

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

B3.4/5.0

Scored across 31 tools

Disambiguation4/5

Most tools have clearly distinct purposes (search, install, compile, run, publish, arena, auth). However, the cluster of read-only stats/reputation tools (get_gene_stats, get_gene_reputation, get_my_reputation, get_leaderboard, get_developer_profile) could cause some hesitation, though descriptions differentiate them.

Naming Consistency4/5

Predominantly snake_case with verb_noun pattern (search_genes, install_gene, compile_gene). Minor deviations like doctor (noun), agent_run/arena_submit (noun_verb order), auth_status (noun_noun) and vg_scan are readable but slightly inconsistent.

Tool Count2/5

31 tools is heavy for the server's scope, exceeding the typical 15-tool threshold. While many operations are distinct, several could be consolidated (e.g., stats/reputation variants, auth group) or exposed as subcommands rather than separate tools.

Completeness4/5

The surface covers discovery, local lifecycle (init, scan, wrap, compile, run, test, install, rollback, publish), agents (list, create, run), auth, arena, analytics, and security scanning. Missing explicit uninstall/delete or update operations for genes/agents, but core workflows are well-covered.

Maintenance

ActivityActive
ResponsivenessUnresponsive