Skip to main content
Glama

haus

by app.onehaus
OverviewDiscussionsAdmin

list_calendar_events

Read-only

List one-off calendar events with their title, times, location and notes. Bound them with startDateFrom and startDateTo, or omit both for everything.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
startDateToNoRange end, ISO 8601 UTC. Matches events starting at or before this.
startDateFromNoRange start, ISO 8601 UTC. Matches events ending, or starting if undated, at or after this.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
itemsYes
titleNo
messageNo
variantNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / startDateFrom / description
      Previous value: -"Inclusive lower bound of the date range, ISO 8601 date-time in UTC. An event matches if it ends (or, when it has no end, starts) on or after this instant. Omit for no lower bound."New value: +"Range start, ISO 8601 UTC. Matches events ending, or starting if undated, at or after this."
    • changedInput schema / properties / startDateTo / description
      Previous value: -"Inclusive upper bound of the date range, ISO 8601 date-time in UTC. An event matches if it starts on or before this instant. Omit for no upper bound."New value: +"Range end, ISO 8601 UTC. Matches events starting at or before this."
  2. Changed5 schema fields changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "startDateFrom": "2026-07-01T00:00:00Z",
+    "startDateTo": "2026-07-31T23:59:59Z"
+  }
+]
    • changedInput schema / properties / startDateFrom / description
      Previous value: -"UTC date range bound (ISO 8601 date-time)"New value: +"Inclusive lower bound of the date range, ISO 8601 date-time in UTC. An event matches if it ends (or, when it has no end, starts) on or after this instant. Omit for no lower bound."
    • addedInput schema / properties / startDateFrom / examples
      Added value: +[
+  "2026-07-01T00:00:00Z"
+]
    • changedInput schema / properties / startDateTo / description
      Previous value: -"UTC date range bound (ISO 8601 date-time)"New value: +"Inclusive upper bound of the date range, ISO 8601 date-time in UTC. An event matches if it starts on or before this instant. Omit for no upper bound."
    • addedInput schema / properties / startDateTo / examples
      Added value: +[
+  "2026-07-31T23:59:59Z"
+]
  3. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, covering the safety profile. The description adds meaningful behavioral context beyond annotations: it explicitly scopes to one-off events and explains that omitting both bounds returns everything, which clarifies the tool's behavior in a way annotations do not.

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?

Two sentences with no filler. The first sentence states the tool's purpose and returned fields, the second conveys the parameter usage rule. Every sentence contributes and the most critical information is front-loaded.

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 simple read-only list tool with a full output schema and 100% schema coverage, the description covers the core behavior and boundary condition. A minor gap is that it doesn't explicitly state what happens if only one date bound is provided, but the schema descriptions and examples largely fill that gap.

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

Parameters4/5

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

Schema description coverage is 100%, so the baseline is 3. The description adds the pairing rule that startDateFrom and startDateTo should be used together or both omitted, which clarifies the relationship between the optional parameters beyond their individual schema descriptions and examples.

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 states the specific verb 'List', the resource 'one-off calendar events', and the fields returned (title, times, location, notes). The qualifier 'one-off' clearly distinguishes it from recurring calendar event operations among siblings, making the tool's scope immediately identifiable.

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?

It provides clear context that this tool lists one-off events and instructs to bound with both date parameters or omit both for everything. However, it names no alternative tools and does not explicitly state when not to use it, relying on the 'one-off' qualifier rather than direct exclusion.

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

All haus 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