Skip to main content
Glama

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
AGENTAOS_API_KEYNoYour AgentaOS API key (process.env.AGENTAOS_API_KEY). Note: with the Claude Code plugin/MCP server you authenticate in your browser instead, so there is no key to paste.

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": true
}

Tools

Functions exposed to the LLM to take actions

NameDescription
agenta_status_getC

Account and go-live overview

agenta_audit_requestC

Ask for the free Revenue & Pricing Audit

agenta_audit_showC

The audit state, and download the report PDF once it exists

agenta_verify_submitC

Submit business verification so the merchant can accept live payments

agenta_verify_statusD

Where the verification has got to

agenta_verify_resubmitB

Send back for review after making the changes we asked for

agenta_verify_declarationD

The five statements --accept-declaration attests to

agenta_products_createB

Create a product (one-time) or a subscription plan

agenta_products_listC

List products and plans

agenta_pay_checkoutC

Create a checkout session

agenta_pay_getB

Get checkout session status

agenta_pay_listC

List checkout sessions

agenta_subscriptions_change_planA

Move a subscription to another plan (upgrade charges now, downgrade at period end)

agenta_subscriptions_listC

List subscriptions

agenta_subscriptions_cancelA

Cancel a subscription (at period end by default)

agenta_customers_listC

List customers

agenta_invoices_listC

List invoices

agenta_invoices_receiptB

Download the receipt PDF for a paid invoice

agenta_invoices_send_receiptC

Re-send the receipt email to the buyer on file

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

C2.8/5.0

Scored across 19 tools

Disambiguation4/5

Tools are largely distinct, with clear resource-action separation (e.g., audit_request vs audit_show, pay_checkout vs pay_get). Minor potential confusion between agenta_status_get (account/go-live overview) and agenta_verify_status (verification progress), but descriptions differentiate them well.

Naming Consistency4/5

Consistent agenta_<resource>_<action> snake_case pattern throughout. Minor deviations: some actions are nouns (status, declaration, receipt) rather than verbs, but the pattern remains predictable.

Tool Count4/5

19 tools is slightly above the ideal 3-15 range but reasonable for a full payments and merchant onboarding platform. Each tool appears to serve a distinct function without obvious redundancy.

Completeness3/5

Core onboarding (audit, verification) and payment workflows (checkout, subscriptions, invoices) are covered. Notable gaps include refund operations, product/customer update or delete, and subscription creation, which may limit agents in some scenarios.

Maintenance

ActivityActive
ResponsivenessUnresponsive