Chrono MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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
| Name | Description |
|---|---|
| GET TIMEA | Get current time or convert times across timezones with flexible formatting. Defaults to current time in system timezone when no parameters provided. Use timezones array to get multiple zones, formats array for multiple output formats. |
| TIME CALCULATORB | Perform time arithmetic operations including duration calculations, date math, interval operations, statistical analysis, and sorting. Use for adding/subtracting time periods, calculating differences between dates, analyzing time-based datasets, or sorting arrays of timestamps. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 2 tools
The two tools have clearly distinct purposes: GET TIME focuses on time retrieval, conversion, and formatting, while TIME CALCULATOR handles arithmetic operations, duration calculations, and data analysis. There is no overlap in functionality, making it easy for an agent to choose the correct tool based on the task.
The naming is mixed: GET TIME uses uppercase with a space, while TIME CALCULATOR uses uppercase with a space but includes a more descriptive term. This inconsistency in style (e.g., no uniform verb_noun pattern) reduces predictability, though the names remain readable and descriptive of their functions.
With only 2 tools, the server feels thin for a time-related domain that could benefit from more operations like scheduling, timezone management, or recurring events. While the tools cover basic needs, the count is borderline low for comprehensive time handling, suggesting potential under-scoping.
The tools cover core time operations (retrieval/conversion and arithmetic/analysis), but there are notable gaps such as scheduling, timezone database updates, or handling recurring events. Agents can work around these with the provided tools, but the surface is not fully complete for advanced time management tasks.