Skip to main content
Glama
huseyindol

User Info MCP Server

by huseyindol

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault

No arguments

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
get_all_usersB

Tüm kullanıcıların listesini getir

get_user_by_idC

ID'ye göre belirli bir kullanıcıyı getir

search_users_by_nameC

İsme göre kullanıcı ara

search_users_by_emailC

E-posta adresine göre kullanıcı ara

search_users_by_phoneC

Telefon numarasına göre kullanıcı ara

add_userC

Yeni kullanıcı ekle

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

B3.4/5.0

Scored across 6 tools

Disambiguation5/5

Each tool has a clearly distinct purpose: add_user creates a new user, get_all_users retrieves all users, get_user_by_id fetches a specific user by ID, and the three search tools each target different attributes (email, name, phone). There is no overlap or ambiguity in functionality.

Naming Consistency5/5

All tool names follow a consistent verb_noun pattern with snake_case (e.g., add_user, get_all_users, search_users_by_email). The naming is predictable and readable throughout the set.

Tool Count5/5

With 6 tools, this server is well-scoped for user information management. The count is appropriate, covering core operations (create, retrieve, search) without being excessive or insufficient for the domain.

Completeness4/5

The tool set covers key user operations: creation (add_user), retrieval (get_all_users, get_user_by_id), and search (by email, name, phone). Minor gaps exist, such as missing update and delete operations, which agents might need to work around, but core workflows are largely supported.

Maintenance

ActivityInactive
ResponsivenessNo issues