Skip to main content
Glama
zakblacki

Satim Payment Gateway Integration

by zakblacki

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
NODE_ENVNoThe application environmentdevelopment
SATIM_BASE_URLNoThe SATIM API base URL (use https://satim.dz/payment/rest for production)https://test.satim.dz/payment/rest
SATIM_PASSWORDYesYour SATIM merchant password
SATIM_USERNAMEYesYour SATIM merchant username
SATIM_TERMINAL_IDNoYour bank-assigned terminal ID

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
configure_credentialsC

Configure SATIM payment gateway credentials

register_orderC

Register a new order with SATIM payment gateway

confirm_orderC

Confirm order status after payment attempt

refund_orderC

Process refund for a completed order

validate_payment_responseC

Validate and interpret payment response status

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

A3.5/5.0

Scored across 5 tools

Disambiguation5/5

Each tool has a clearly distinct purpose with no overlap: configure_credentials handles setup, register_order initiates payments, validate_payment_response processes responses, confirm_order checks status, and refund_order handles refunds. The descriptions make it easy for an agent to select the right tool for each payment workflow step.

Naming Consistency5/5

All tools follow a consistent verb_noun pattern with clear action verbs (configure, confirm, refund, register, validate) and specific nouns (credentials, order, payment_response). The naming is uniform and predictable throughout the set.

Tool Count5/5

Five tools is well-scoped for a payment gateway integration, covering the essential operations: setup, order registration, response validation, status confirmation, and refunds. Each tool earns its place without redundancy or obvious gaps.

Completeness5/5

The tool set provides complete coverage for the payment gateway domain, including configuration, order lifecycle (register, confirm, refund), and response validation. There are no dead ends or missing operations for typical payment processing workflows.

Maintenance

ActivityInactive
ResponsivenessNo issues