Chronos MCP

get_events_range

Retrieve all events from a specified calendar within a given start and end date. Filter by account if needed.

Instructions

Get events within a date range

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "calendar_uid": "<calendar_uid>",
      "start_date": "<start_date>",
      "end_date": "<end_date>"
    },
    "name": "get_events_range"
  }
}

Input Schema

Name	Required	Description
`account`	No	Account alias
`end_date`	Yes	End date (ISO format)
`start_date`	Yes	Start date (ISO format)
`calendar_uid`	Yes	Calendar UID

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv2.1.0Jul 12, 2026

TDQS

C2.9/5.0

Behavior2/5

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

The verb 'Get' implies a read-only operation, but no additional behavioral traits are disclosed. With no annotations, the description should specify that it does not modify data, what happens with empty results, or any side effects. Currently, it is minimal.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Single sentence, 5 words, with the verb front-loaded. Extremely concise, but could benefit from a bit more structure or detail without becoming verbose. Still effective for a simple tool.

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

Completeness3/5

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

Given the tool's simplicity and the presence of an output schema, the description combined with schema is adequate. However, it lacks context about calendar requirement, date inclusivity, and how it differs from search_events, which has similar functionality.

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 each parameter has a description. The tool description adds no extra meaning beyond the schema, such as explaining the optional account parameter or date format nuances. Baseline 3 is appropriate.

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?

Description clearly states the action (Get), resource (events), and constraint (within a date range). It differentiates from siblings like search_events, create_event, etc., but could explicitly mention that events are tied to a specific calendar.

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 tool vs alternatives like search_events or list_calendars. No mention of prerequisites, exclusions, or when not to use it.

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