Skip to main content
Glama
danfmaia

Utility MCP Server

by danfmaia
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
READ_AI_API_KEYNoAPI key for Read.AI platform (required for download_meeting_data tool)

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
get_current_datetimeA
Get the current date and time in the specified timezone and format.

Args:
    timezone_name: Timezone name (e.g., "UTC", "US/Eastern", "Europe/London", "America/Sao_Paulo")
    format_type: Format type ("iso", "readable", "timestamp", "custom")

Returns:
    Current datetime in the requested format
calculate_time_differenceA
Calculate the time difference between two datetimes or from a start time to now.

Args:
    start_datetime: Start datetime in ISO format (YYYY-MM-DD HH:MM:SS or YYYY-MM-DDTHH:MM:SS)
    end_datetime: End datetime in ISO format (optional - defaults to current time)
    timezone_name: Timezone for interpretation (default: UTC)

Returns:
    Time difference with detailed breakdown
download_meeting_dataC
Download meeting transcript and/or summary from Read.AI.

Args:
    meeting_id: Read.AI meeting ID
    include_transcript: Whether to download the full transcript (default: True)
    include_summary: Whether to download the meeting summary (default: True)

Returns:
    Meeting data in formatted text or JSON structure
util_server_statusB
Check the status of all utility server integrations.

Returns:
    Status report of available utilities and their configuration

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

Deploy Server
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

TDQS

A3.5/5.0

Scored across 4 tools

Disambiguation5/5

Each tool has a clearly distinct purpose with no overlap: time calculation, meeting data download, current datetime retrieval, and server status check. The descriptions clearly differentiate their functions, eliminating any risk of misselection.

Naming Consistency4/5

Three tools follow a consistent verb_noun pattern (calculate_time_difference, download_meeting_data, get_current_datetime), but util_server_status deviates by using a noun_verb_noun structure. The deviation is minor and doesn't significantly impact readability.

Tool Count4/5

Four tools is reasonable for a utility server, though slightly thin for covering multiple domains like time and meeting data. Each tool earns its place, but the scope feels a bit broad for just four tools.

Completeness3/5

For the time-related tools, there's basic coverage (calculate difference, get current time), but missing operations like timezone conversion or date arithmetic. For meeting data, download is covered but no create/update/delete. The server status tool is standalone. Notable gaps exist that agents may need to work around.

Maintenance

ActivityInactive
ResponsivenessNo issues

Resources