Skip to main content
Glama

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
TRENDYOL_API_KEYNoTrendyol API key for live data
HEPSIBURADA_API_KEYNoHepsiburada API key for live data
TRENDYOL_API_SECRETNoTrendyol API secret for live data
TRENDYOL_SUPPLIER_IDNoTrendyol supplier ID for live data
HEPSIBURADA_MERCHANT_IDNoHepsiburada merchant ID for live data
HEPSIBURADA_MERCHANT_NAMENoHepsiburada merchant name (optional)

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
}

Tools

Functions exposed to the LLM to take actions

NameDescription
list_ordersC

Son siparişleri listeler (durum ve tarih filtresiyle). Salt okunur.

list_returnsC

İade ve talep kayıtlarını listeler. Salt okunur.

stock_alertsB

Stok eşiğinin altına düşen ürünleri, tükenenler önce olacak şekilde döndürür.

sla_breachesB

Hazırlık süresini aşan veya teslim sözü geçmiş siparişleri bulur.

return_clustersB

Son N günde aynı nedenle tekrarlayan iadeleri gruplar (iade kök nedeni).

unanswered_reviewsC

Cevapsız kalmış olumsuz ürün yorumlarını bulur.

price_overviewA

Fiyat tutarsızlıklarını (listeden yüksek fiyat, olağandışı indirim) raporlar.

daily_digestC

Tüm kuralları çalıştırır ve önceliklendirilmiş Türkçe aksiyon listesi üretir.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

B3.2/5.0

Scored across 8 tools

Disambiguation4/5

Most tools target clearly distinct concerns (stock, SLA, reviews, pricing, digest), and descriptions explain each. Minor overlap exists: list_orders vs sla_breaches both surface orders, and list_returns vs return_clusters both involve returns, though granularity and intent differ.

Naming Consistency4/5

All names use consistent snake_case, which is good. However verb style is mixed: list_orders/list_returns use verb_noun while the rest (stock_alerts, sla_breaches, daily_digest, etc.) are noun phrases, a minor deviation.

Tool Count5/5

Eight tools is well-scoped for a seller-operations alerting/monitoring server. Each tool corresponds to a distinct monitoring domain or aggregation, so none feels redundant or filler.

Completeness4/5

The surface covers orders, returns, stock, SLA, reviews, pricing, and a roll-up digest, giving broad monitoring coverage with no dead ends. It is entirely read-only, so any action-taking (replying to reviews, adjusting stock) is out of scope, but that appears intentional for an insights toolset.

Maintenance

ActivityMaintained
ResponsivenessNo issues