Skip to main content
Glama
Crawlora MCP

Crawlora MCP

Official

fever_plan

Get a single Fever plan's structured detail record—venues, coordinates, images, labels, advertised from-price, and session dates—as compact JSON instead of the heavier Angular page.

Instructions

Get one Fever plan's detail record. Returns one Fever (feverup.com) plan: name, description, canonical page, city, category labels, advertised from-price, every place it happens at with coordinates, gallery images, the first and last session dates, translation languages and the plan's own session flags. This reads Fever's JSON plan route rather than the Angular page that carries the same record, so one plan costs a few kilobytes instead of a few hundred. An unknown plan id is a 404. The price is the advertised starting price and is volatile; it is never a final or purchasable price, and no ticket, session-availability or checkout data is returned.

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": {
      "plan_id": "<plan_id>"
    },
    "name": "fever_plan"
  }
}

Input Schema

NameRequiredDescriptionDefault
plan_idYesNumeric Fever plan id from fever-plans

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.20

TDQS

A3.9/5.0
Behavior4/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 does substantial work: it discloses the payload size tradeoff (JSON route vs Angular page, kilobytes vs hundreds of kilobytes), the 404 behavior for unknown ids, and explicitly enumerates what is NOT returned (tickets, session availability, checkout). It stops short of auth requirements, rate limits, or caching behavior, keeping it out of the top band.

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?

Front-loaded with the core action, then field inventory, then caveats — a sensible order. The middle sentence about reading JSON instead of the Angular page is slightly self-justifying, but it earns its place by explaining the payload advantage.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

There is no output schema, and the description compensates by enumerating the return fields in detail (places with coordinates, gallery images, first/last session dates, translation languages, session flags) and by flagging the volatility of the price field. For a one-parameter detail lookup, an agent has everything needed to call it and interpret the result correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% for the single plan_id parameter, so the baseline is 3; the description adds real value by stating that an unknown id yields a 404 and that the id is numeric and sourced from the Fever plan listing. This is error semantics the schema cannot express.

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 opening sentence gives a specific verb and resource: 'Get one Fever plan's detail record,' which is plainly distinguishable from the plural list sibling fever_plans. The enumeration of returned fields (name, description, places, gallery, session dates) reinforces the single-record scope, though the description never names a sibling to contrast against.

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 through the 'one plan' framing and the note that plan_id comes from a listing tool; there is no explicit 'use this when you have an id, use fever_plans/fever_feed to discover ids' statement. The 404 note on unknown ids is the closest thing to a precondition, and no exclusions are stated.

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