Skip to main content
Glama
Sign In

Crawlora MCP

by net.crawlora
OverviewDiscussionsAdmin

luma_place_events

Read-only

Lists or searches public Luma events for a place. 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": {
      "place_slug": "<place_slug>"
    },
    "name": "luma_place_events"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryNoLuma event search text
place_slugYesLuma place page slug
pagination_limitNoPage size; Luma returns at most 50 entries
pagination_cursorNoOpaque cursor returned by Luma

Output Schema

NameRequiredDescriptionDefault
dataYesThe tool result payload (shape varies per tool; see each tool's docs resource).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnly and openWorld, so the bar is lower, and the description still adds real behavior: results are limited to public events and the cursor/has_more continuation loop is spelled out. It does not mention rate limits or ordering, so it is not exhaustive, but it goes meaningfully beyond the annotations.

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, and the pagination rule is placed after the core purpose where it is actionable. Every sentence carries information an agent needs.

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 an output schema present, the description needn't document return values, and it correctly focuses on scope and the pagination loop instead. An agent could call this correctly from the description plus schema, though it would still be guessing about result ordering and the meaning of a missing place.

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 every parameter is already documented, which sets the baseline at 3. The description only adds the pairing between the returned has_more flag and the pagination_cursor input, without clarifying query matching semantics or the 50-item cap beyond what the schema states.

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?

Uses a specific verb ('Lists or searches') plus a well-scoped resource ('public Luma events for a place'), so an agent can tell this apart from calendar- or category-scoped siblings. It does not explicitly name any sibling as an alternative, which keeps it 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 only implied: passing a query means search, omitting it means list, and the second sentence gives operational guidance for pagination. There is no statement of when to prefer this over luma_place, luma_place_calendars, or luma_calendar_events, and no prerequisites mentioned.

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

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