Crawlora MCP

luma_category_events

Read-only

Lists or searches public Luma events in a category. Continue with the returned cursor 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. Documented values: family, books, games, tech, food, ai, running, arts, climate, fitness, wellness, crypto.
`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

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

A3.8/5.0

Behavior4/5

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

With readOnlyHint and openWorldHint already declaring the safety profile, the description adds two useful behavioral details beyond annotations: results are limited to public events, and the returned cursor must be followed while has_more is true. It leaves out whether coordinates switch the feed to a nearby mode or how results are ordered, but the pagination contract is the most actionable item and it is disclosed.

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, purpose first, pagination follow-up second. Every clause carries information and nothing is padded.

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?

An output schema exists, so return-value explanation is unnecessary, and six parameters are fully documented in the schema. The description covers purpose and pagination adequately; the only residual gap is hinting at what the optional coordinate parameters change about the feed.

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 slug values, query text, coordinates and page size are already documented in the schema. The description only echoes the cursor concept already in pagination_cursor and adds no new semantics such as how latitude/longitude interact with slug.

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 ('Lists or searches public Luma events in a category') and the category scoping distinguishes it from calendar- and place-scoped siblings. It stops short of naming which sibling to use for those other scopes, so an agent still has to infer the boundary.

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?

'Lists or searches' implies the list-vs-search split via the query parameter, but the description never states when to pick this over luma_place_events or luma_calendar_events, nor any exclusion. Usage is implied rather than guided.

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?