Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

luma_event

Retrieve public Luma event details by event API ID, including categories, host display names, and ticket availability while omitting guest, payment, and private calendar data.

Instructions

Get a public Luma event. Returns public event details, categories, host display names, and ticket availability fields. Guest identities, payment data, and private calendar fields are omitted.

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": {
      "event_api_id": "<event_api_id>"
    },
    "name": "luma_event"
  }
}

Input Schema

NameRequiredDescriptionDefault
event_api_idYesPublic Luma event id returned by an event feed

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.20

TDQS

B3.4/5.0
Behavior3/5

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

With no annotations supplied, the description carries the full burden, and it does add real value by enumerating what is returned and which sensitive fields (guest identities, payment data, private calendar fields) are deliberately omitted. It is silent on important behavior for a public-only read: what happens for a private, cancelled, or nonexistent event id, whether auth affects results, and whether pagination or rate limits apply.

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?

Three tight sentences: purpose first, then return contents, then privacy exclusions. No filler, no restatement of the tool name, and the most decision-relevant fact (public only) is front-loaded.

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?

For a one-parameter read tool with no annotations and no output schema, the description covers purpose, payload shape, and data exclusions adequately. The remaining gap is failure/edge-case behavior for non-public or invalid event ids, which matters given the explicit 'public' scoping.

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% for the single event_api_id parameter, so the schema already explains format and provenance. The description adds no meaning about the id beyond confirming the tool operates on public events, which is the expected baseline of 3 when the schema does the heavy lifting.

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 ('Get a public Luma event') plus the nature of the payload, so an agent knows this is a single-event lookup rather than a listing or search. It does not explicitly position itself against luma_calendar_events or luma_category_events, but the singular 'an event' plus the id requirement makes the distinction inferable.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no when-to-use or when-not guidance and no named alternative for discovering events versus fetching one. The only implied usage ('public' events) comes from an adjective, not an explicit condition, so an agent must infer when to call this instead of the calendar/category/place listing tools.

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