Skip to main content
Glama

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
FUNPAY_PROXYNoProxy URL, e.g., socks5://localhost:1080
FUNPAY_LOCALENoLocale: ru, en, or ukru
FUNPAY_TIMEOUTNoHTTP timeout in seconds15
FUNPAY_GOLDEN_KEYYesValue of the golden_key cookie (required)
FUNPAY_USER_AGENTNoUser-Agent of the browser with an active FunPay sessionChrome 124 Linux

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": false
}
prompts
{
  "listChanged": false
}
resources
{
  "subscribe": false,
  "listChanged": false
}
experimental
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
get_meD
get_userD
get_balanceD
get_chatsD
get_chat_historyD
send_messageD
get_salesD
get_orderD
refundD
get_my_lotsD
get_lot_fieldsD
save_lotD
delete_lotD
get_categoriesD
get_subcategoriesD
raise_lotsD

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

C2/5.0

Scored across 16 tools

Disambiguation4/5

Most tools are clearly distinct, such as get_me vs get_user and get_chats vs get_chat_history. However, get_sales and get_order could be confused since both relate to transactions, and get_my_lots vs get_lot_fields might be ambiguous without clear descriptions.

Naming Consistency5/5

All tool names follow a consistent verb_noun pattern with lowercase and underscores (e.g., get_balance, send_message, delete_lot). Even exceptions like refund and raise_lots still adhere to the pattern, creating a predictable and uniform naming scheme.

Tool Count4/5

With 16 tools, the server is slightly above the ideal 3-15 range, but the breadth is justified by the need to cover user, order, lot, chat, and category management. No tools feel redundant, and the count is not overwhelming.

Completeness4/5

The toolset covers core marketplace workflows well: user profiles, balance, refunds, sales/orders, lot CRUD (save/delete/get), and categories. Missing operations like explicit lot search or order creation are minor gaps, as buyers would normally initiate these actions.

Maintenance

ActivitySlowing
ResponsivenessNo issues