Skip to main content
Glama

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
mcp_call_conda_infoA

Get comprehensive information about the Conda installation on this system.

If env_name is provided, it will return the information for the specified
environment as well.

Returns detailed information including:
- Conda version and configuration
- Python version and virtual packages
- Base environment location
- Channel URLs and package cache locations
- Platform and system details
- Complete list of all Conda environments with their paths
- Complete list of all packages in the specified environment and their versions

This is useful for diagnosing Conda-related issues or understanding
the Python environment configuration on this system.
mcp_call_mac_system_profilerA
Call the system_profiler with the given datatype. Allow LLM to deepdive into the
system information.
This function is used to get the system information to help user to understand the
system and potentially debug.

Allowed datatypes:
    - SPAirPortDataType - Airport/WiFi information
    - SPApplicationsDataType - Application information
    - SPAudioDataType - Audio device information
    - SPBluetoothDataType - Bluetooth information
    - SPCameraDataType - Camera information
    - SPDiagnosticsDataType - Diagnostic information
    - SPDisplaysDataType - Display and graphics information
    - SPFirewallDataType - Firewall settings
    - SPHardwareDataType - Hardware specifications
    - SPLocationDataType - Location services information
    - SPMemoryDataType - Memory information
    - SPNetworkDataType - Network settings and interfaces
    - SPNVMeDataType - NVMe storage details
    - SPPCIDataType - PCI devices information
    - SPPowerDataType - Battery and power information
    - SPSoftwareDataType - Software and OS information
    - SPStorageDataType - Storage devices and volumes
    - SPThunderboltDataType - Thunderbolt ports and connections
    - SPUSBDataType - USB devices and connections
mcp_call_gpu_availableA
Check if GPU is available in torch for a specific conda environment.
Input: torch or tensorflow
if framework is not provided, it will default to torch.

Returns a detailed dictionary with the following information:
- "torch_version": PyTorch version string
- "python_version": Python version string
- "platform": Platform information string
- "processor": Processor type
- "architecture": CPU architecture
- "mps_available": True if MPS (Metal Performance Shaders) is available
- "mps_built": True if PyTorch was built with MPS support
- "mps_functional": True if MPS is functional, False otherwise
- "benchmarks": A list of benchmark results for different matrix sizes, each containing:
  - "size": Matrix size used for benchmark
  - "cpu_time": Time taken on CPU (seconds)
  - "mps_time": Time taken on MPS (seconds)
  - "speedup": Ratio of CPU time to MPS time (higher means MPS is faster)

This helps determine if GPU acceleration via Apple's Metal is properly configured
and functioning, with performance benchmarks for comparison.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

A4/5.0

Scored across 3 tools

Disambiguation5/5

Each tool has a clearly distinct purpose with no overlap: conda_info focuses on Conda environments, gpu_available checks GPU availability and performance, and mac_system_profiler retrieves system information. The descriptions clearly differentiate their domains, making misselection unlikely.

Naming Consistency5/5

All tools follow a consistent 'mcp_call_' prefix with descriptive snake_case suffixes (conda_info, gpu_available, mac_system_profiler). This uniform pattern makes the tool set predictable and easy to understand.

Tool Count3/5

With only 3 tools, the server feels thin for a 'my-mac' system management scope. While the tools cover Conda, GPU, and system profiling, there are likely other Mac/system-related operations missing, making the set feel incomplete rather than well-scoped.

Completeness2/5

For a Mac system management server, there are significant gaps: no tools for file operations, process management, network utilities, or basic system commands. The three tools provide deep but narrow coverage, leaving many common system tasks unaddressed and likely causing agent failures for broader requests.

Maintenance

ActivityInactive
ResponsivenessNo issues