Skip to main content
Glama
dknell

System Information MCP Server

by dknell

get_memory_info_tool

Retrieve memory usage statistics to monitor system performance and identify resource constraints in real-time.

Instructions

Retrieve memory usage statistics.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • The MCP tool handler function for 'get_memory_info_tool'. It is registered using the @app.tool() decorator and executes the tool logic by calling the underlying get_memory_info() helper function.
    @app.tool()
    def get_memory_info_tool() -> Dict[str, Any]:
        """Retrieve memory usage statistics."""
        return get_memory_info()
  • The core helper function implementing the memory information retrieval using psutil.virtual_memory() and psutil.swap_memory(). It includes caching via @cache_result decorator and provides detailed virtual and swap memory statistics.
    @cache_result("memory_info", ttl=1)
    def get_memory_info() -> Dict[str, Any]:
        """Retrieve memory usage statistics."""
        try:
            # Get virtual memory info
            virtual_mem = psutil.virtual_memory()
    
            # Get swap memory info
            swap_mem = psutil.swap_memory()
    
            return {
                "virtual_memory": {
                    "total": virtual_mem.total,
                    "available": virtual_mem.available,
                    "used": virtual_mem.used,
                    "percent": round(virtual_mem.percent, 1),
                    "total_gb": bytes_to_gb(virtual_mem.total),
                    "available_gb": bytes_to_gb(virtual_mem.available),
                    "used_gb": bytes_to_gb(virtual_mem.used),
                },
                "swap_memory": {
                    "total": swap_mem.total,
                    "used": swap_mem.used,
                    "free": swap_mem.free,
                    "percent": round(swap_mem.percent, 1),
                    "total_gb": bytes_to_gb(swap_mem.total),
                },
            }
    
        except Exception as e:
            logger.error(f"Error getting memory info: {e}")
            raise
Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations are provided, so the description carries full burden. It states 'retrieve' implying a read operation, but lacks details on permissions, rate limits, response format, or any behavioral traits. This is inadequate for a tool with zero annotation coverage.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single, efficient sentence with no wasted words. It's appropriately sized and front-loaded, clearly stating the tool's purpose without unnecessary elaboration.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's simplicity (0 parameters, output schema exists), the description is minimally complete. However, with no annotations and multiple siblings, it lacks guidance on usage and behavioral context, making it adequate but with clear gaps.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool has 0 parameters with 100% schema description coverage, so the schema fully documents the lack of inputs. The description adds no parameter info, but with no parameters, this is acceptable, aligning with the baseline for 0 parameters.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the verb ('retrieve') and resource ('memory usage statistics'), making the purpose understandable. However, it doesn't differentiate from sibling tools like get_cpu_info_tool or get_disk_info_tool beyond the resource name, missing explicit sibling distinction.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides no guidance on when to use this tool versus alternatives. With multiple sibling tools for system info (e.g., get_cpu_info_tool, get_disk_info_tool), there's no indication of context, exclusions, or prerequisites for selecting this specific tool.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/dknell/mcp-system-info'

If you have feedback or need assistance with the MCP directory API, please join our Discord server