Skip to main content
Glama
ilil1

Simple MCP Server

by ilil1

system_info

Retrieve basic system information to monitor device status and performance metrics.

Instructions

Get basic system information.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The handler function for the 'system_info' tool. It logs a message and returns a dictionary containing the Python version, system name, and platform details.
    def system_info() -> dict:
        """Get basic system information."""
        logger.info("system_info called")
        return {
            "python_version": platform.python_version(),
            "system": platform.system(),
            "platform": platform.platform(),
        }
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states the tool 'Get[s]' information, implying a read-only operation, but doesn't specify if it requires permissions, has rate limits, returns real-time vs. cached data, or what format the output takes. For a tool with zero annotation coverage, this is a significant gap in transparency.

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 ('Get basic system information.') that is front-loaded and wastes no words. It directly communicates the core purpose without unnecessary elaboration, making it highly concise and well-structured for its simplicity.

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 low complexity (0 parameters, no output schema, no annotations), the description is minimally complete. It states what the tool does but lacks details on behavioral traits, output format, or usage context. This is adequate for a basic tool but leaves gaps that could hinder an agent's understanding in more complex scenarios.

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 input schema has 0 parameters with 100% description coverage, so no parameter documentation is needed. The description doesn't add parameter details beyond the schema, which is appropriate here. A baseline of 4 is applied as it adequately handles the lack of parameters without introducing confusion.

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 'Get basic system information' clearly states the verb ('Get') and resource ('basic system information'), making the purpose immediately understandable. It distinguishes from siblings like 'get_version' (which likely returns version-specific data) and 'hello_world' (a test endpoint) by focusing on general system details. However, it doesn't specify what 'basic' entails (e.g., OS, memory, CPU), keeping it from a perfect score.

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?

No guidance is provided on when to use this tool versus alternatives like 'get_version'. The description implies it's for retrieving system information but doesn't clarify if 'get_version' is a subset or a different type of data, nor does it mention any prerequisites or exclusions. This leaves the agent without explicit usage context.

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/ilil1/simple-mcp-server'

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