Skip to main content
Glama

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
LITHIC_API_KEYNoLithic API key for virtual card shopping
PAYPAL_CLIENT_IDNoPayPal client ID
STRIPE_SECRET_KEYNoStripe secret key for payment processing
LITHIC_ENVIRONMENTNoLithic environment: production or sandboxproduction
PAYPAL_ENVIRONMENTNoPayPal environment: production or sandboxproduction
PAYPAL_CLIENT_SECRETNoPayPal client secret

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
setup_lithicA

Set up Lithic virtual card API for AI shopping. Reads LITHIC_API_KEY from environment.

browse_and_buyA

Browse an online store, add items to cart, and complete purchase using a Lithic virtual card. Requires Playwright installed.

setup_paymentB

Set up Stripe payment method for ClawPay.

payC

Create and confirm a payment in cents.

get_balanceB

Get Stripe account balance.

list_transactionsC

List recent payment transactions.

refundB

Refund a payment intent.

setup_paypalA

Link PayPal account using Client ID and Client Secret. Reads credentials from PAYPAL_CLIENT_ID and PAYPAL_CLIENT_SECRET environment variables or config file.

send_paypalB

Send money via PayPal Payouts to an email address or phone number.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

B3.2/5.0

Scored across 9 tools

Disambiguation4/5

Most tools have distinct purposes (shopping, Stripe payments, PayPal payouts, setup), though 'pay' and 'send_paypal' could be confused without reading descriptions. Overall clear boundaries.

Naming Consistency2/5

Naming convention is inconsistent: mix of single verbs ('pay', 'refund'), verb_verb ('browse_and_buy'), and verb_noun patterns. No consistent structure.

Tool Count4/5

9 tools cover multiple payment workflows and setup, which is appropriate for the domain. Not overly numerous or sparse.

Completeness3/5

Covers core actions (pay, refund, send) but missing some operations like PayPal refund, Stripe payment cancellation, or detailed payment retrieval beyond listing.

Maintenance

ActivityInactive
ResponsivenessNo issues