MCP Time Server

Get Days in Month

days_in_month

Read-onlyIdempotent

Find the number of days in any month by supplying a date. Returns the day count for that month's calendar.

Instructions

Returns the number of days in the month of a given date.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "days_in_month"
  }
}

Input Schema

Name	Required	Description	Default
`date`	No	The date to check (format: YYYY-MM-DD). Defaults to current date

Output Schema

Name	Required	Description	Default
`days`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.0.5Aug 1, 2026

TDQS

A3.8/5.0

Behavior3/5

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

Annotations already indicate read-only and idempotent behavior, so the agent knows it is safe. The description adds no additional behavioral details such as leap-year handling or timezone dependence, but it also introduces no contradictions.

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, focused sentence that gets straight to the point with no unnecessary words.

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?

The tool is simple with one optional parameter, strong annotations, and an output schema. The description adequately identifies the purpose while the schema handles parameter details; no critical information appears missing.

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

Parameters3/5

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

The description does not mention the 'date' parameter; however, the input schema fully covers it with format and default value. With 100% schema coverage, the description need not add parameter semantics.

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 the action (returns) and the resource (number of days in a month for a given date). This distinguishes it from sibling tools like relative_time or get_timestamp, which serve different time/date purposes.

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

Usage Guidelines3/5

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

The description gives no explicit guidance on when to choose this tool over alternatives (e.g., current_time or convert_time). Usage is implied by the function—needing days in a month—but no alternatives or exclusions are mentioned.

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

Deploy Server