Sentinel
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 | {
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| create_cardB | Mint a new virtual card funded from the wallet. [Sentinel: policy-enforced; may return status denied_by_sentinel or approval_required_by_sentinel with a machine-readable reason chain.] |
| get_card_detailsC | Retrieve full card number and CVV for a card. |
| list_cardsA | List cards created for this user. |
| check_balanceB | Check the wallet balance. |
| close_cardC | Deactivate a card. |
| list_transactionsC | List transactions for a card. |
| list_all_transactionsB | List transactions across all cards. |
| buy_add_to_cartC | Add an item to the cart at a linked merchant. |
| buy_view_cartC | View the current cart at a merchant, with the priced total. |
| buy_checkoutA | Place and pay for the current cart at a linked merchant. [Sentinel: policy-enforced; may return status denied_by_sentinel or approval_required_by_sentinel with a machine-readable reason chain.] |
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 10 tools
Each tool targets a distinct action: card management (create, list, close, get details), transaction queries (single card vs all), balance check, and purchasing flow (add to cart, view cart, checkout). The 'buy_' prefix clearly separates merchant actions from card operations, eliminating ambiguity.
All tool names follow a consistent verb_noun pattern using snake_case (e.g., list_cards, close_card, buy_add_to_cart). The only minor variance is 'check_balance' instead of 'get_balance', but it remains a clear verb_noun structure, maintaining high consistency.
With 10 tools, the server covers the essential operations for virtual card management and merchant purchasing without being overwhelming. Each tool serves a necessary function in the workflow, making the count well-scoped for the domain.
The tool set covers core card lifecycle and basic transactions, but lacks merchant management (e.g., linking merchants), wallet funding, and cart modification (remove/update items). These gaps may cause agents to get stuck when the workflow requires actions outside the provided surface.