Skip to main content
Glama
tim-akkio

MCP Server Framework

by tim-akkio

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
PYTHONPATHYesPath to the src directory, required for the server to find the package modules (e.g., /path/to/mcp-server/src).
MCP_LOG_LEVELNoLogging level (DEBUG, INFO, WARNING, ERROR)INFO
MCP_SERVER_NAMENoDisplay name for the servermcp-server
MCP_ALLOWED_PATHSNoComma-separated absolute paths for file tools. Required if using file operation tools.

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
echoB
    Echo back the provided message.

    Args:
        message: The message to echo back

    Returns:
        The same message, confirming receipt
    
echo_uppercaseA
    Echo back the message in uppercase.

    Args:
        message: The message to transform and echo

    Returns:
        The message converted to uppercase
    
echo_reverseA
    Echo back the message reversed.

    Args:
        message: The message to reverse

    Returns:
        The message with characters in reverse order
    
get_current_timeA
    Get the current date and time in UTC.

    Args:
        format: strftime format string (default: %Y-%m-%d %H:%M:%S)

    Returns:
        Formatted current date/time string in UTC
    
parse_timestampA
    Convert a Unix timestamp to a human-readable format.

    Args:
        timestamp: Unix timestamp (seconds since epoch)
        format: strftime format string

    Returns:
        Formatted date/time string in UTC
    
get_timestampA
    Get the current Unix timestamp.

    Returns:
        Current time as Unix timestamp (seconds since epoch)
    
time_differenceB
    Calculate the difference between two timestamps.

    Args:
        start_timestamp: Start Unix timestamp
        end_timestamp: End Unix timestamp

    Returns:
        Human-readable time difference
    
list_directoryA
    List contents of a directory.

    Requires MCP_ALLOWED_PATHS to be configured with permitted directories.

    Args:
        path: Directory path to list

    Returns:
        Formatted directory listing or error message
    
read_fileA
    Read contents of a text file.

    Requires MCP_ALLOWED_PATHS to be configured with permitted directories.

    Args:
        path: File path to read
        max_lines: Maximum number of lines to return (default: 100)

    Returns:
        File contents or error message
    
get_file_infoA
    Get information about a file or directory.

    Requires MCP_ALLOWED_PATHS to be configured with permitted directories.

    Args:
        path: Path to get info about

    Returns:
        File information or error message
    
get_allowed_pathsB
    Get the list of allowed file system paths.

    Returns:
        List of configured allowed paths or instructions to configure
    

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

A3.7/5.0

Scored across 11 tools

Disambiguation4/5

Most tools have distinct purposes, but there is some overlap between time-related tools. get_current_time, get_timestamp, and parse_timestamp all handle time data, which could cause confusion about which to use for specific scenarios. However, their descriptions clarify their differences: get_current_time returns formatted UTC, get_timestamp returns Unix seconds, and parse_timestamp converts Unix to formatted. The echo variants are clearly distinct in their transformations.

Naming Consistency5/5

All tool names follow a consistent snake_case pattern with clear verb_noun structures. Examples include echo_reverse, get_allowed_paths, list_directory, and parse_timestamp. There are no deviations in naming conventions, making the set predictable and easy to understand at a glance.

Tool Count4/5

With 11 tools, the count is reasonable for a framework server, but it feels slightly over-scoped due to redundancy. The three echo tools and multiple time tools could potentially be consolidated without losing functionality. However, the number is within the typical 3-15 range and covers basic utility operations adequately.

Completeness3/5

The server covers basic utility functions like echoing, time handling, and file operations, but there are notable gaps. For file operations, it provides get_file_info, list_directory, and read_file, but lacks write, delete, or update capabilities, which are common in file management. The time tools are comprehensive, but the overall domain of 'framework' is vague, making it hard to assess full coverage beyond these utilities.

Maintenance

ActivityInactive
ResponsivenessNo issues