Crawlora MCP

Official

Overview Schema Source Related Servers Discussions Admin

luma_category_events

Search and list public events in a Luma category using its slug, with optional query, coordinates, and pagination filters to retrieve event cards.

Instructions

List and search events in a Luma category. Returns public event cards in a Luma category. The category slug must be one of family, books, games, tech, food, ai, running, arts, climate, fitness, wellness, or crypto. Query, cursor, page limit, and optional coordinates mirror Luma's category feed. Follow next_cursor only when has_more is true.

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_category_events"
  }
}

Input Schema

Name	Required	Description
`slug`	Yes	Luma category slug
`query`	No	Luma event search text
`latitude`	No	Optional latitude used by Luma's nearby category feed
`longitude`	No	Optional longitude used by Luma's nearby category feed
`pagination_limit`	No	Page size; Luma returns at most 50 entries
`pagination_cursor`	No	Opaque cursor returned by Luma

Schema Changelog

Changes observed during successful MCP inspections.

Addedv1.17.20Nov 12, 2026

TDQS

B3.4/5.0

Behavior3/5

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

With no annotations, the description carries the full burden and does disclose useful behavior: results are public event cards, the feed mirrors Luma's category feed, and cursors should only be followed when has_more is true. It does not mention auth requirements, rate limits, ordering, or what a card contains, which leaves meaningful gaps for a read tool with zero annotation coverage.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The opening two sentences overlap heavily ('List and search events in a Luma category' / 'Returns public event cards in a Luma category'), and the full twelve-value enum duplicates the schema. The pagination guidance is valuable and front-loaded at the end, but the definition could shed a sentence without losing information.

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?

No output schema exists, yet the description names the return shape ('public event cards') and the pagination fields (next_cursor, has_more) that an agent needs to iterate correctly. Given a simple six-parameter list tool, this is close to sufficient, though per-card fields and coordinate behavior remain unspecified.

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%, so the schema already documents all six parameters, including the slug enum and the 50-entry page cap. The description's note that query, cursor, page limit, and coordinates 'mirror Luma's category feed' adds only light framing beyond the schema, and it repeats the slug enum verbatim rather than adding meaning.

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 and search events in a Luma category') and scopes the result to public event cards. The category qualifier implicitly separates it from sibling feeds like luma_place_events or luma_calendar_events, but no sibling is named, so an agent must infer the distinction from the resource noun alone.

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 only implied: the tool is for browsing a Luma category feed, and the description does not say when to prefer it over place, calendar, or search-oriented alternatives, nor any prerequisites. The pagination rule ('Follow next_cursor only when has_more is true') is the only explicit operating instruction.

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

Deploy Server