Skip to main content
Glama
Sign In

mcp-time

by io.github.mcpcentral-io
OverviewDiscussionsAdmin

Get Days in Month

days_in_month

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

Input Schema

NameRequiredDescriptionDefault
dateNoThe date to check. Format: YYYY-MM-DD

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • removedInput schema / $schema
      Removed value: -"http://json-schema.org/draft-07/schema#"
    • removedInput schema / additionalProperties
      Removed value: -false
    • changedInput schema / properties / date / description
      Previous value: -"The date to check (format: YYYY-MM-DD). Defaults to current date"New value: +"The date to check. Format: YYYY-MM-DD"
    • changedOutput schema / (root)
      Previous value: -{
-  "$schema": "http://json-schema.org/draft-07/schema#",
-  "additionalProperties": false,
-  "properties": {
-    "days": {
-      "type": "integer"
-    }
-  },
-  "required": [
-    "days"
-  ],
-  "type": "object"
-}New value: +null
  2. Changed4 schema fields changed
    • addedInput schema / $schema
      Added value: +"http://json-schema.org/draft-07/schema#"
    • addedInput schema / additionalProperties
      Added value: +false
    • changedInput schema / properties / date / description
      Previous value: -"The date to check. Format: YYYY-MM-DD"New value: +"The date to check (format: YYYY-MM-DD). Defaults to current date"
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": false,
+  "properties": {
+    "days": {
+      "type": "integer"
+    }
+  },
+  "required": [
+    "days"
+  ],
+  "type": "object"
+}
  3. First observed

TDQS

B3.4/5.0
Behavior3/5

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

No annotations are provided, but this is a pure computation with no side effects, and the description states what it returns. It does not mention leap-year handling, which is the one non-obvious behavioral edge for this 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?

A single front-loaded sentence with no filler; every word earns its place.

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?

For a one-parameter pure function with no output schema and full schema coverage, the description is essentially complete. Only leap-year semantics are left unstated.

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?

Schema coverage is 100%, so the date parameter's format (YYYY-MM-DD) is already documented. The description adds only that the month component of the date is what matters, which is marginal value.

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?

States a specific verb and resource: 'Returns the number of days in the month of a given date.' An agent can tell this apart from siblings like get_week_year or current_time, though it doesn't explicitly name the distinction.

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 on when to use this versus the sibling time utilities (e.g., get_week_year, get_timestamp). For a simple utility the need is mild, but nothing is stated.

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

All mcp-time toolsInspect
Try in Browser
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

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources