Skip to main content
Glama
knowitcz

mcp-week-day

by knowitcz
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

mcp-week-day

A small MCP server built with FastMCP. It exposes a single tool, day_in_week, which returns the current day of the week — "Monday", "Tuesday", …

Requirements

  • Python 3.10+

Related MCP server: mcp-local-gateway

Setup & run from scratch

Using uv (recommended)

# Run the server
uv run mcp-week-day

First run might take some time as a virtual environment will be created and dependencies will be installed into it.

Using pip

# Create and activate a virtual environment
python -m venv .venv
source .venv/bin/activate        # on Windows: .venv\Scripts\activate

# Install the project (+ dependencies)
pip install -e .

# Run the server
mcp-week-day

The server communicates over stdio using the MCP protocol.

Register with an MCP client

Add an entry like this to your client's MCP configuration:

{
  "mcpServers": {
    "week-day": {
      "command": "uv",
      "args": ["run", "mcp-week-day"]
    }
  }
}

If you installed with pip into an activated environment, you can instead use "command": "mcp-week-day" with no args.

Tool

Tool

Arguments

Returns

day_in_week

none

The current weekday name, e.g. "Monday".

Available Tools

1 tool
day_in_weekA

Return the current day of the week (e.g. "Monday", "Tuesday").

ParametersJSON Schema
NameRequiredDescriptionDefault

No parameters

Output Schema

ParametersJSON Schema
NameRequiredDescription
resultYes

TDQS

A4.6/5.0
Behavior4/5

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

The description plainly states that the tool returns the current day of the week, making the behavior transparent. No side effects are mentioned, but the description is sufficiently clear for a read-only operation.

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, providing the essential information in a single sentence without any superfluous content.

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

Completeness5/5

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

The description fully specifies what the tool returns (the day of the week) and even gives examples, which is sufficient given no parameters and no output schema details. Nothing essential is missing.

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

Parameters5/5

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

The tool has no parameters, so there is nothing to add beyond the empty schema. The description correctly implies no inputs are required.

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

Purpose5/5

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

The description clearly states a specific action ('Return') and a specific resource ('the current day of the week'), with examples. No ambiguity.

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

Usage Guidelines4/5

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

No explicit guidance on when to use this tool, but there are no sibling tools or alternatives, so the context is implicitly clear. The absence of alternatives makes explicit usage instruction unnecessary.

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

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

  1. 1 tool updatev0.1.0
    • First observedday_in_week
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

A4.3/5.0

Scored across 1 tool

Disambiguation5/5

Only one tool exists, so there is no possibility of overlap or confusion.

Naming Consistency5/5

The single tool name 'day_in_week' is clear, descriptive, and follows a consistent snake_case convention.

Tool Count2/5

A single tool feels extremely minimal for a general-purpose MCP server, even if the domain is narrowly focused on weekdays.

Completeness2/5

The tool only returns the current weekday; it lacks related functionality such as date formatting, day number, or validation, leaving the surface quite thin.

Maintenance

ActivityMaintained
ResponsivenessNo issues

Resources

Related MCP Connectors

Related MCP Servers

  • mcp-local-gateway

    SongLei75
    F
    license
    Not graded
    quality
    B
    maintenance
    Minimal MCP server exposing a single tool, run_date, to execute the local date command via a Streamable HTTP endpoint.
    -

  • hello-world-mcp

    emokhtareg
    A
    license
    A
    quality
    C
    maintenance
    A minimal MCP server that provides a single 'hello' tool returning 'Hello, world!'.
    2
    6 npm
    MIT

  • helloworld-demo-mcp

    Jasonrve
    F
    license
    Not graded
    quality
    C
    maintenance
    A minimal MCP server offering a hello_world tool that returns a greeting and current UTC time via streamable HTTP.
    -