Skip to main content
Glama
yusuferenkt

MCP JSON Database Server

by yusuferenkt

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
NODE_ENVNoThe Node.js environment modeproduction

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
registerC

Yeni kullanıcı kaydı oluşturur

loginC

Kullanıcı giriş yapar ve JWT token alır

verify_tokenC

JWT token'ın geçerliliğini kontrol eder

change_passwordC

Kullanıcı şifresini değiştirir

get_my_permissionsC

Kullanıcının sahip olduğu yetkileri listeler

list_call_transcriptsC

Telefon görüşmeleri transkriptlerini listeler

get_call_transcript_by_idC

ID'ye göre telefon transkripti getirir

search_call_transcriptsC

Transkriptlerde anahtar kelime arama yapar

add_call_transcriptC

Yeni telefon görüşmesi transkripti ekler

update_call_transcriptC

Mevcut transkripti günceller

get_call_analyticsC

Çağrı analitikleri ve istatistikleri getirir

list_usersB

Tüm kullanıcıları listeler (Yetki gerekli)

get_user_by_idC

ID'ye göre kullanıcı bilgilerini getirir (Yetki gerekli)

search_usersC

Kullanıcıları ad, email, departman veya pozisyona göre arar

add_userC

Yeni kullanıcı ekler

update_userC

Mevcut kullanıcı bilgilerini günceller

delete_userD

Kullanıcıyı siler

get_my_audit_logsC

Kullanıcının kendi audit loglarını getirir

get_all_audit_logsB

Tüm audit logları getirir (Sadece admin)

get_audit_logs_by_categoryC

Belirli kategorideki audit logları getirir (Admin/Manager)

get_audit_logs_by_dateB

Belirli tarih aralığındaki audit logları getirir (Admin/Manager)

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

B3/5.0

Scored across 21 tools

Disambiguation4/5

Most tools have distinct purposes, but some overlap exists: get_audit_logs_by_category and get_audit_logs_by_date both retrieve audit logs with different filters, which could cause confusion if not carefully described. However, tools generally target clear resources like users, call transcripts, or authentication, making them mostly distinguishable.

Naming Consistency5/5

Tool names follow a consistent verb_noun pattern throughout, such as add_user, delete_user, get_user_by_id, and update_user. This predictability aids in understanding and usage, with no deviations in style or convention across the set.

Tool Count3/5

With 21 tools, the count feels heavy for a JSON database server, suggesting potential over-scoping. While it covers user management, call transcripts, and audit logs, the number may overwhelm agents and could be streamlined without losing functionality.

Completeness5/5

The tool set provides comprehensive coverage for its inferred domains: user management (CRUD operations, authentication), call transcripts (add, get, list, search, update), and audit logs (various retrieval methods). No obvious gaps exist, supporting complete workflows from login to data management.