Skip to main content
Glama

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
NODE_ENVNoNode.js environment (development or production)development
JWT_SECRETYesSecret key for JWT token signing
DATABASE_URLYesPostgreSQL connection string for Neon database
KINDE_CLIENT_IDYesKinde client ID for OAuth authentication
KINDE_ISSUER_URLYesKinde authentication issuer URL (e.g., https://your-domain.kinde.com)
KINDE_CLIENT_SECRETYesKinde client secret for OAuth authentication

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

Server capabilities have not been inspected yet.

Tools

Functions exposed to the LLM to take actions

NameDescription
loginB

Login with Kinde to get authentication token

save_tokenC

Save your Kinde authentication token for future use

list_todosC

List all todos for the authenticated user

get_subscription_statusC

Get the user's subscription status and todo usage

upgrade_subscriptionC

Upgrade user subscription to paid plan

create_todoC

Create a new todo item with interactive prompts

update_todoC

Update an existing todo item with interactive prompts

delete_todoC

Delete a todo item with interactive prompts

logoutA

Logout and clear stored authentication token

get_kinde_billingC

Get Kinde billing information and subscription status

refresh_billing_statusB

Force refresh billing status from Kinde (useful after plan changes)

logoutA

Logout and clear stored authentication token

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 11 tools

Disambiguation3/5

The todo management tools (create_todo, delete_todo, list_todos, update_todo) are clearly distinct and cover the CRUD operations well. However, there is some ambiguity between get_kinde_billing and get_subscription_status, as both seem to retrieve subscription-related information, and refresh_billing_status overlaps with these. The authentication tools (login, logout, save_token) are distinct from the todo tools but have some functional overlap with each other.

Naming Consistency4/5

Most tools follow a consistent verb_noun pattern (e.g., create_todo, list_todos, update_todo, get_kinde_billing, refresh_billing_status). The main deviation is 'login' and 'logout', which use a single verb without a noun, but this is a common convention for authentication actions. Overall, the naming is predictable and readable with only minor inconsistencies.

Tool Count4/5

With 11 tools, the count is reasonable for a server that combines todo management with authentication and billing features. It's slightly on the higher side but not excessive, as it covers multiple domains (todos, auth, billing) within a coherent scope. The tools are well-distributed across these areas without obvious bloat.

Completeness4/5

For todo management, the server provides complete CRUD coverage (create, list, update, delete). Authentication is covered with login, logout, and token management. Billing features include status retrieval, refresh, and upgrade. A minor gap is the lack of a tool to downgrade or cancel subscriptions, but the core workflows are well-supported.

Maintenance

ActivityInactive
ResponsivenessNo issues