Skip to main content
Glama

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault

No arguments

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
{
  "listChanged": false
}

Tools

Functions exposed to the LLM to take actions

NameDescription
noetic.connectA

Open a session. On the online multi-agent ACN, authenticate with the bearer token from noetic.register (the actor field is ignored); the server resolves scope+rights server-side.

noetic.capabilitiesC

Discover the grantable capability vocabulary within scope.

noetic.disconnectB

End a session (durable facts are not revoked).

noetic.orientC

Narrated state + scope-projected delta from a checkpoint.

noetic.diffC

Scope-projected delta between two checkpoints.

noetic.observeC

Grounded Γ observation for a subject, or the budgeted cluster narration when no subject.

noetic.focusC

Drill a summary's focusRef into full per-entity detail.

noetic.queryC

Raw geometric query: entities at/above a divergence, scope-projected.

noetic.reasonD

AGORA exegesis: the divergent cluster as a typed inference (narrowing scope optional).

noetic.groundD

Drill a phenomenon to its measurement evidence, scope-projected.

noetic.recallC

Read committed assertions another session left about a subject (shared-context recall).

noetic.locateD

Where an in-scope entity sits, metric-version-bound.

noetic.territoryD

District organization + declared-vs-lived gap (typed inference).

noetic.authorityC

Dry-run permission probe for an in-scope target.

noetic.proposeC

Create a private, non-authoritative assertion (hypothesis|inference|intent only).

noetic.simulateC

Private, non-persisted what-if over an entity.

noetic.materializeC

Turn a simulation into an inference|hypothesis (reserved kinds rejected).

noetic.mutateC

Request a governed change (needs mutate right + intent + authority policy).

noetic.confirmD

The sole requires-governance→authoritative path (governance capability only).

noetic.commitB

Persist a session's produced records (validates ownership, state, non-stale base).

noetic.checkpointD

Reference a checkpoint at the current state.

noetic.create_spaceC

Create a geometric space (partition) in the account dump (owner-governed; fails closed at the space cap).

noetic.storeC

Authoritative ingestion of context objects (observation|declaration|measurement) into a space; fails closed at the object cap.

noetic.fetchA

Read the raw content of a space's stored objects (owner, or a grant carrying read); optional case-insensitive substring query + limit. Metered as one query.

noetic.grantA

Grant a principal scoped rights + persistence mode on a space (owner-governed; narrowing-only).

noetic.revokeA

Revoke a prior grant (owner-governed; future authorization only, never rewrites receipts).

noetic.check_rightsB

Preflight dry-run: would this operation be allowed, and at what price (not metered).

noetic.set_pricingC

Set the owner-defined pricing schedule for a space (owner-governed).

noetic.usageC

Report usage, cost and (for owners) revenue for an authorized principal, account-bounded.

noetic.receiptB

Fetch or verify a usage receipt by id (unsigned in MVP, integrity-checked).

noetic.persistC

Write a derivative into a target space, honoring the source persistence mode (propose->commit).

noetic.publishA

Set a space's discovery visibility: public (listed in noetic.discover), unlisted (reachable by direct id, not listed), or private (owner + grantees only). Owner-governed; defaults to public.

noetic.metricsB

Developer metrics: role-scoped account + per-space counters (caps, headroom, resident tokens, queries, cost) plus measured server runtime (calls, errors, read-latency percentiles). Not metered.

noetic.registerA

Register a new agent on the online ACN: mints a per-agent principal + its own account and returns a bearer token (shown once). Present the token to noetic.connect.

noetic.rotate_tokenA

Rotate this agent's bearer token: mints a fresh token and immediately retires the old one (leak recovery or periodic rotation). Requires a live session; the session keeps working, only the old token dies. The new token is shown once.

noetic.discoverA

List publicly available spaces across all accounts (name, owner, offered rights, size, pricing) so an agent can decide what to request access to. Read-only; no object content.

noetic.request_accessA

Request a grant on a space you do not own (public or unlisted). Records a pending request the space owner can approve or deny.

noetic.list_requestsA

List access requests visible to you: requests on spaces you own (to decide) plus requests you have made (to track).

noetic.approve_requestA

Approve a pending access request on a space you own, issuing the grant (optionally narrowing rights / persistence / world-mutation). Owner-governed.

noetic.deny_requestB

Deny a pending access request on a space you own. Owner-governed.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

C2.4/5.0

Scored across 40 tools

Disambiguation2/5

Many tools have overlapping or highly specialized purposes that are hard to distinguish without deep domain knowledge (e.g., noetic.observe vs noetic.query vs noetic.reason vs noetic.ground; noetic.propose vs noetic.simulate vs noetic.materialize). The descriptions use dense jargon, making it difficult for an agent to reliably select the right tool.

Naming Consistency3/5

The naming is mostly consistent with a noetic. prefix and verb-style names (connect, disconnect, query, commit, grant, revoke). However, some names are abstract or inconsistent in style (e.g., noetic.orient, noetic.territory, noetic.focus, noetic.ground) and don't follow a clear verb_noun pattern like others.

Tool Count2/5

40 tools is a very large surface for a single server, and many tools are highly specialized or overlapping. While the server appears to cover a complex domain, the count feels excessive and would likely overwhelm an agent, especially with many niche operations (e.g., noetic.orient, noetic.territory, noetic.metrics).

Completeness4/5

The tool set covers a broad lifecycle: registration, connection, spaces, grants, access requests, assertions, checkpoints, commits, and receipts. There are some potential gaps (e.g., no explicit tool for deleting a space or revoking a session), but the surface is fairly comprehensive for the apparent domain.

Maintenance

ActivityMaintained
ResponsivenessNo issues