Skip to main content
Glama
danfmaia

Utility MCP Server

by danfmaia

util_server_status

Check the status and configuration of all utility server integrations to monitor operational health and available tools.

Instructions

Check the status of all utility server integrations.

Returns:
    Status report of available utilities and their configuration

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • The handler function for the 'util_server_status' tool, decorated with @mcp.tool() for automatic registration. It generates a comprehensive status report including integration availability (e.g., Read.AI), tool listings, and server information.
    @mcp.tool()
    async def util_server_status() -> str:
        """
        Check the status of all utility server integrations.
    
        Returns:
            Status report of available utilities and their configuration
        """
    
        status = "Utility Server Status\n"
        status += "===================\n\n"
    
        # Read.AI Integration
        status += "**Read.AI Meeting Downloader**\n"
        status += f"- Available: {'✅ Yes' if readai_client.is_available() else '❌ No (API key needed)'}\n"
        status += f"- API Base URL: {readai_client.base_url}\n"
        if not readai_client.is_available():
            status += "- Configuration: Set READ_AI_API_KEY environment variable\n"
            status += "- Development: Mock data available for testing\n"
        status += "\n"
    
        # Datetime Tools
        status += "**DateTime Tools**\n"
        status += "- Available: ✅ Yes (no configuration needed)\n"
        status += "- Timezone Support: Full pytz timezone database\n"
        status += "- Formats: ISO, readable, timestamp, custom\n"
        status += "\n"
    
        # Server Info
        status += "**Server Information**\n"
        status += "- Framework: FastMCP\n"
        status += "- Tools Available: 4\n"
        status += "- Purpose: General-purpose utilities for productivity\n"
        status += "\n"
    
        # Available Tools
        status += "**Available Tools**\n"
        status += "1. `get_current_datetime` - Get current date/time in any timezone and format\n"
        status += "2. `calculate_time_difference` - Calculate time differences with detailed breakdown\n"
        status += "3. `download_meeting_data` - Download Read.AI meeting transcripts and summaries\n"
        status += "4. `util_server_status` - Check utility server status and configuration\n"
        status += "\n"
    
        # Future Expansion
        status += "**Expansion Ready**\n"
        status += "This server is designed to house multiple simple utility tools.\n"
        status += "New tools can be easily added without creating separate MCP servers.\n"
    
        return status
Behavior2/5

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

With no annotations provided, the description carries full burden for behavioral disclosure. It states the tool 'checks' status and returns a report, which implies a read-only operation, but doesn't specify if it requires authentication, has rate limits, or affects system state. The description adds minimal behavioral context beyond the basic action, missing details like whether it performs active probing or returns cached data.

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 extremely concise and well-structured. The first sentence directly states the tool's purpose, and the 'Returns:' section clearly indicates the output without unnecessary elaboration. Every sentence earns its place, with no redundant or vague phrasing, making it easy to parse quickly.

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

Completeness4/5

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

Given the tool's simplicity (zero parameters, no annotations, but with an output schema), the description is reasonably complete. It explains what the tool does and what it returns, and the output schema will handle return value details. However, it lacks context about the utility integrations (e.g., what types, why check them), which could help an agent understand when this tool is relevant.

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 zero parameters, and the input schema has 100% description coverage (though empty). The description appropriately doesn't discuss parameters, as none exist. It could theoretically mention that no inputs are required, but this is adequately covered by the schema. The baseline for zero parameters is 4, as the description doesn't need to compensate for any parameter documentation gaps.

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 tool's purpose with a specific verb ('Check') and resource ('status of all utility server integrations'), making it immediately understandable. It distinguishes itself from siblings like 'calculate_time_difference' or 'download_meeting_data' by focusing on system status rather than data processing or retrieval. However, it doesn't explicitly differentiate from potential similar tools (e.g., 'check_server_health'), which prevents 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?

The description provides no guidance on when to use this tool versus alternatives. It doesn't mention prerequisites, timing considerations, or suggest using other tools for related tasks. For example, it doesn't clarify if this should be used before invoking utility-dependent tools like 'download_meeting_data', leaving usage context entirely implicit.

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/danfmaia/util-mcp'

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