Crawlora MCP

Official

Overview Schema Source Related Servers Discussions Admin

luma_calendar_events

List public Luma calendar events for a chosen calendar, filtering by future, past, or a specific RFC3339 date range to find upcoming or historical events.

Instructions

List events for a public Luma calendar. Returns public future, past, or date-specific events for one calendar. period accepts future, past, or specific; the last value requires RFC3339 after and before timestamps.

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_api_id": "<calendar_api_id>"
    },
    "name": "luma_calendar_events"
  }
}

Input Schema

Name	Required	Description
`after`	No	RFC3339 start time; required for period=specific
`before`	No	RFC3339 end time; required for period=specific
`period`	No	Calendar event period
`calendar_api_id`	Yes	Calendar API id from luma-place-calendars
`pagination_limit`	No	Page size; 0 returns all entries in the selected period
`pagination_cursor`	No	Opaque cursor returned by Luma

Schema Changelog

Changes observed during successful MCP inspections.

Addedv1.17.20Nov 12, 2026

TDQS

A3.5/5.0

Behavior3/5

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

No annotations are provided, so the description carries the full behavior burden; it does disclose the public-only visibility constraint and what kinds of events come back (future, past, or date-ranged). It says nothing about pagination cost, whether pagination_limit=0 is expensive, rate limits, or auth requirements — relevant given a 'return all entries' option.

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?

Two tight sentences, front-loaded with what the tool returns, followed by the period/parameter constraint. No filler or redundant framing; only minor gain from condensing further.

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?

With no annotations and no output schema, the description does enough for a six-parameter read tool: it establishes scope, returnable event sets, and the one conditional-parameter rule. Pagination behavior is left entirely to the schema, which is acceptable given full schema coverage but is a small residual gap.

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 100%, so all six parameters are already documented inline. The description restates the period enum and the after/before requirement for period=specific, reinforcing but not extending the schema; no new meaning is added for pagination_limit or pagination_cursor.

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 — 'List events for a public Luma calendar' — and narrows the scope to public future/past/date-specific events for a single calendar. It does not name any sibling (e.g. luma_category_events or luma_place_events) to disambiguate which event-listing tool to pick, so it stops short of a 5.

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?

Usage is implied through the 'public calendar' scope and the period vocabulary, which hints this is for enumerating a calendar's events rather than category- or place-scoped listings. There is no explicit when-to-use/when-not-to-use guidance or reference to alternatives, so the agent must infer routing from names alone.

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

Deploy Server