Skip to main content
Glama
Sign In

Crawlora MCP

by net.crawlora
OverviewDiscussionsAdmin

luma_category

Read-only

Returns public details and featured calendars for one current Luma event category.

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

Input Schema

NameRequiredDescriptionDefault
slugYesLuma category slug. Documented values: family, books, games, tech, food, ai, running, arts, climate, fitness, wellness, crypto.

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.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds that the returned data is 'public' and that the payload includes 'featured calendars', which is modest but genuine context beyond the annotations. It says nothing about caching, freshness of 'current' categories, or failure behavior for an invalid slug.

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

Conciseness4/5

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

One front-loaded sentence with no filler; the verb and the two things returned (details and featured calendars) come first. Slightly terse for the amount of routing information a caller needs, but nothing is wasted.

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?

The tool is simple (one required param, full schema coverage, and an output schema that documents return values), so the description does not need to explain the response shape. It covers what is fetched and its scope; only the sibling-routing guidance is missing.

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% and the slug parameter already lists the documented category values, so the schema carries the semantics. The description only adds the qualifier 'current', hinting the category must exist in the live taxonomy, without explaining what happens for retired or unknown slugs. Baseline 3 is appropriate.

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?

The description gives a specific verb ("Returns") and a specific resource ("public details and featured calendars for one current Luma event category"), which distinguishes it from the list-style sibling luma_categories and the event-listing sibling luma_category_events. It stops short of naming those siblings, but an agent can infer the distinction from the singular 'one category' framing.

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 singular 'one current Luma event category' signals this is a per-category detail lookup rather than a browse-all call. There is no explicit guidance on when to choose this over luma_categories (to discover slugs) or luma_category_events (to get the events themselves), and no stated prerequisites for the slug.

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