Skip to main content
Glama

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
AWS_REGIONNoAWS region for Bedrock
OLLAMA_URLNoURL of the Ollama serverhttp://localhost:11434
GROQ_API_KEYNoAPI key for Groq
BEDROCK_MODEL_IDNoBedrock model ID
AWS_ACCESS_KEY_IDNoAWS access key for Bedrock
AWS_SECRET_ACCESS_KEYNoAWS secret access key for Bedrock

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
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
compute_routeC

Route a query to the best available compute provider (Bedrock → Groq → Ollama). Returns result wrapped in Magma envelope.

ere_verifyB

Run ERE 5-pass verification on a content string. Returns pass/fail per pod and METATRON certification.

proxy_registerB

Register a named proxy tool at a URL. Proxied tools are callable via agent_dispatch.

proxy_list

List all registered proxy tools and their status.

magma_sealB

Wrap any content in a Magma envelope with ERE verification and WORM hash.

agent_dispatchA

Dispatch a task to a registered proxy tool or sovereign agent. Runs ERE gate before forwarding.

magma_execA

Execute a Magma instruction string. Parses §VERB:AGENT:ACTION{payload}, routes to the correct executor (COMPUTE→Bedrock, QUERY→Groq, SEAL→WORM, DISPATCH→proxy), signs result with governor Ed25519 key, and returns Magma envelope. Supports pipeline syntax with >>.

governor_pubkeyA

Return the governor public key (base64 Ed25519 SPKI DER). Use this to verify Magma envelope signatures externally.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

A3.6/5.0

Scored across 7 tools

Disambiguation4/5

Tools have mostly clear boundaries, but `agent_dispatch` and `compute_route` could be confused for routing tasks, and `magma_exec` is a meta-tool that overlaps with several others. Still, descriptions are detailed enough to differentiate.

Naming Consistency4/5

Names follow a consistent `<system>_<action>` pattern (e.g., `ere_verify`, `proxy_register`) except `compute_route` which reverses the order. Otherwise well-structured.

Tool Count5/5

7 tools cover the core functionality without bloat. Each tool serves a distinct purpose and the set feels well-scoped for a sovereign computation system.

Completeness4/5

Covers primary operations (routing, verification, sealing, dispatch, execution, key retrieval). Missing explicit tools for verifying signatures or listing proxies, but the existing set handles core workflows.

Maintenance

ActivityMaintained
ResponsivenessNo issues