Skip to main content
Glama

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
MP_CURRENCYNoDefault currency (defaults to ARS)ARS
MP_SUCCESS_URLNoDefault success redirect URL for payment preferences
WA_NOTIFY_PHONENoPhone number for WhatsApp payment notifications
TELEGRAM_BOT_TOKENNoTelegram bot token from @BotFather
WHATSAPP_ACCESS_TOKENNoMeta Graph API token
WHATSAPP_VERIFY_TOKENNoWebhook verification token
WHATSAPP_PHONE_NUMBER_IDNoWhatsApp Business phone number ID
MERCADO_PAGO_ACCESS_TOKENYesMercado Pago API access token
MERCADO_PAGO_WEBHOOK_SECRETNoHMAC secret for Mercado Pago webhook signature validation

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
create_payment_preferenceC

Creates a Mercado Pago checkout payment preference (payment link). Returns init_point URL for redirecting buyers.

get_paymentC

Retrieve a payment by its ID. Returns full payment details including status, amount, payer info.

create_refundA

Refund a payment fully or partially. Omit amount for full refund.

search_paymentsB

Search recent payments for the authenticated merchant. Supports filtering by status.

get_merchant_infoB

Retrieve the authenticated merchant's user profile including ID, nickname, and site.

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

Disambiguation5/5

Each tool has a clearly distinct purpose with no ambiguity. create_payment_preference handles payment initiation, create_refund manages refunds, get_merchant_info retrieves merchant data, get_payment fetches specific payment details, and search_payments searches multiple payments. The descriptions clearly differentiate their functions, making misselection unlikely.

Naming Consistency5/5

All tool names follow a consistent verb_noun pattern using snake_case. The verbs (create, get, search) are applied logically to their respective nouns (payment_preference, refund, merchant_info, payment, payments), creating a predictable and readable naming convention throughout the set.

Tool Count5/5

With 5 tools, the server is well-scoped for payment processing with Mercado Pago. Each tool earns its place by covering core operations: payment creation, refunds, merchant information retrieval, payment lookup, and payment searching. This count is neither too sparse nor bloated for the domain.

Completeness4/5

The tool set provides strong coverage for key payment workflows, including creation, retrieval, searching, and refunds. A minor gap exists in the lack of update or cancellation tools for payments or preferences, but agents can likely work around this given the available operations cover most essential tasks.

Maintenance

ActivityInactive
ResponsivenessUnresponsive