allternit-ops
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
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
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| stripe_charges_enabledA | Check whether the Allternit Stripe account can currently accept charges (read-only). Returns charges_enabled and any pending verification requirements. |
| stripe_list_recent_invoicesB | List recent Stripe invoices (read-only). |
| stripe_send_invoiceA | Draft (and optionally send) a Stripe invoice by wrapping send_invoice.py. Defaults to a dry run that creates the draft and prints totals without sending — pass confirm:true to actually finalize and send. |
| cloudflare_list_pages_projectsA | List Cloudflare Pages projects via wrangler (read-only). |
| cloudflare_deploy_pagesA | Deploy a directory to a known Cloudflare Pages project. Without confirm:true, only prints the command that would run — does not deploy. |
| brain_searchA | Search allternit-brain markdown docs for a text query (case-insensitive substring match). Returns matching file paths, line numbers, and lines. |
| brain_readA | Read a specific allternit-brain doc by path relative to the brain root (e.g. "company/offer.md"). |
| model_routeA | Look up which model tier/backend to use for a task class, per model-routing.json (Allternit's A:// tier policy). Only meaningful when explicitly spawning a subagent or an autonomous agent — an already-running interactive session stays on its own model. |
| client_new_folder_skeletonA | Create a new client folder under Allternit LLC/06_Client_Ops_and_Contracts// and copy in the standard business-ops-kit templates (MSA, SOW, Intake, NDA, Change Order, Support/SLA), named per the kickoff playbook convention. Does not create Stripe customers or send anything — those steps stay manual per the playbook. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 9 tools
Each tool has a distinct domain prefix (stripe_, cloudflare_, brain_, model_, client_) and a unique verb+noun combination, ensuring no ambiguity. For example, stripe_send_invoice is clearly separate from stripe_list_recent_invoices.
All tool names follow a consistent pattern of <domain>_<verb>_<noun> in lowercase with underscores. No mixing of conventions like camelCase or different verb styles.
9 tools is well-scoped for an operations server covering multiple subdomains. Each tool serves a clear purpose without redundancy.
The tool set covers core operations for Stripe, Cloudflare, documentation, model routing, and client onboarding. Minor gaps exist (e.g., no Stripe customer creation), but these are explicitly noted as manual steps.