Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

luma_calendar

Retrieve a public Luma calendar by slug to view its details, tags, featured items, and initial upcoming events; use calendar events tool for past or date-specific feeds.

Instructions

Get a public Luma calendar. Returns public calendar details, its current tags, featured items and initial upcoming events from the public calendar page. Personal, membership, subscription and payment fields are omitted. Use luma-calendar-events for past or date-specific feeds.

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

NameRequiredDescriptionDefault
slugYesPublic Luma calendar slug, such as philosophy

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.20

TDQS

A4.2/5.0
Behavior4/5

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

No annotations exist, so the description carries the full burden and does reasonably well: it discloses the source (the public calendar page), the data shape, the omission of personal/membership/subscription/payment fields, and that events are only 'initial upcoming'. It stops short of stating rate limits, auth expectations, or how many initial events are returned.

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?

Four short sentences, front-loaded with what the tool does and what it returns, then the omissions, then the sibling routing. No redundant or filler wording.

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?

There is no output schema, and the description compensates by enumerating the returned fields and what is excluded. The only real gap is the unspecified size/shape of the 'initial upcoming events' list and any 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 coverage is 100% with a single required slug parameter whose description already says 'Public Luma calendar slug, such as philosophy'. The description's phrase 'public calendar page' reinforces the public-only scope but adds no syntax or format detail beyond the schema.

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 and resource ('Get a public Luma calendar'), enumerates what is returned (calendar details, current tags, featured items, initial upcoming events), and explicitly distinguishes the tool from the sibling that handles past/date-specific data. An agent can select this without opening the 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?

Gives an explicit alternative and the condition that selects it ('Use luma-calendar-events for past or date-specific feeds'), which implies this tool covers the current snapshot. It does not spell out prerequisites beyond the public slug, but the routing guidance is clear.

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

Deploy Server

Other Tools