Crawlora MCP

luma_calendar

Read-only

Gets public calendar details, per-calendar tags, featured events and the initial upcoming feed from a public calendar slug. Use luma_calendar_events for past or date-specific entries.

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": {
      "slug": "<slug>"
    },
    "name": "luma_calendar"
  }
}

Input Schema

Name	Required	Description	Default
`slug`	Yes	Public Luma calendar slug, such as philosophy

Output Schema

Name	Required	Description	Default
`data`	Yes	The tool result payload (shape varies per tool; see each tool's docs resource).

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 8, 2026

TDQS

A4/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so safety and external-dependency behavior are covered. The description contributes the useful nuance that the upcoming feed is "initial" (i.e., a bounded first page) rather than complete, but says nothing about rate limits, auth needs, or whether non-existent slugs error out.

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, no filler, with the capability list front-loaded and the disambiguation sentence last. Every clause maps to something an agent needs to decide or call correctly.

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 simple (one required param), an output schema exists so return shape needn't be explained, and annotations cover the safety profile. The only residual ambiguity is how large the "initial upcoming feed" is and whether pagination exists, which would be nice but is not essential to invoke correctly.

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% and the schema already describes slug with an example ("philosophy"), so the description's repeated "public calendar slug" phrasing adds little new meaning. Baseline 3 is appropriate when the schema carries the parameter documentation.

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?

States a specific verb ("Gets") and enumerates the exact resources returned: calendar details, per-calendar tags, featured events, and the initial upcoming feed, all scoped to a public calendar slug. It also names the sibling luma_calendar_events, so an agent can distinguish it without opening either schema.

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?

Explicitly routes past or date-specific queries to luma_calendar_events, which is a clear when-to-use-this-instead signal. It does not state prerequisites or exclusions beyond that, but the primary branching decision between this tool and its closest sibling is covered.

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

All Crawlora MCP 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?