Skip to main content
Glama

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
WOOVI_APP_IDYesAPI key for the Woovi/OpenPix provider
JUNTO_PER_TX_MAXNoMax single transaction in cents20000
JUNTO_DAILY_LIMITNoMax total spend per day in cents50000
JUNTO_CONFIRM_ABOVENoAsk human before sending if the amount in cents exceeds this threshold5000
JUNTO_ALLOWED_PROVIDERSNoComma-separated allowlist of providers
JUNTO_ALLOWED_DESTINATIONSNoComma-separated type allowlist of destinations

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
payC

Send money to a destination via the best available provider. Amount in cents.

chargeC

Create a payment request, invoice, or QR code.

statusB

Check payment or charge status by correlation ID.

refundB

Refund a completed payment by correlation ID.

balanceB

Check available funds on a payment provider.

providersA

List configured payment providers and their capabilities.

limitsA

Check current spending limits and today's usage (all values in cents).

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

A3.6/5.0

Scored across 7 tools

Disambiguation5/5

Each tool has a clearly distinct purpose with no ambiguity: balance checks funds, charge creates payment requests, limits checks spending, pay sends money, providers lists providers, refund processes refunds, and status checks status. The descriptions clearly differentiate these operations, making it easy for an agent to select the right tool.

Naming Consistency5/5

All tool names follow a consistent, simple noun-based pattern (balance, charge, limits, pay, providers, refund, status) that is readable and predictable. There are no deviations in style or convention, making the set coherent and easy to navigate.

Tool Count5/5

With 7 tools, this server is well-scoped for payment processing, covering key operations like checking funds, creating charges, sending payments, listing providers, handling refunds, and checking status. Each tool earns its place without feeling excessive or insufficient for the domain.

Completeness4/5

The tool set provides strong coverage for core payment workflows, including create (charge), read (balance, limits, providers, status), and update/delete-like actions (pay, refund). A minor gap is the lack of a tool for updating payment details or managing providers beyond listing, but agents can likely work around this with existing tools.

Maintenance

ActivityInactive
ResponsivenessNo issues