RetailHardHat

List Calendar Events

list_calendar_events

Read-onlyIdempotent

Read calendar events in an explicit date range. Omitted dates default to the current UTC calendar month; use explicit dates for the user's local reporting window. MCP approval requirements are configurable by the organization administrator; business workflow approvals always apply.

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": "list_calendar_events"
  }
}

Input Schema

Name	Required	Description	Default
`end`	No		2026-11-30
`start`	No		2026-11-01

Output Schema

Name	Required	Description	Default
`data`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedNov 1, 2026
- changedInput schema / properties / end / default
```
Previous value: -"2026-10-31"New value: +"2026-11-30"
```
- changedInput schema / properties / start / default
```
Previous value: -"2026-10-01"New value: +"2026-11-01"
```
First observedOct 27, 2026

TDQS

A3.9/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint=false, and destructiveHint=false. The description adds useful behavior beyond that: omitted dates default to the current UTC calendar month, and approval requirements may apply depending on organization configuration and business workflows.

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?

The description is front-loaded with the core behavior and default-date rule. The approval sentence is relevant context but slightly ancillary to the tool's primary action, keeping it from being maximally tight.

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 low-complexity with two optional date parameters, rich annotations, and an output schema. The description covers purpose, date defaults, timezone considerations, and approval caveats, leaving only minor gaps such as range inclusivity or pagination behavior.

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 description coverage is 0%, so the description must compensate. It explains that omitted dates default to the current UTC month and that explicit dates should be used for the user's local reporting window, but it does not clarify whether the range is inclusive/exclusive or any maximum range constraints.

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?

The description states a specific verb and resource: 'Read calendar events in an explicit date range.' It is clear what the tool does, but it does not distinguish itself from any sibling because there is no calendar-related sibling tool listed.

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?

It explains when to use explicit dates versus relying on defaults for the current UTC month, and mentions the user's local reporting window. It does not describe when not to use the tool or name alternatives, but the usage context is clear for a read-only listing tool.

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

All RetailHardHat tools Inspect

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

Need Help?