Skip to main content
Glama
Sign In

Crawlora MCP

by net.crawlora
OverviewDiscussionsAdmin

ticketweb_venue

Read-only

Fetch TicketWeb venue details and one page of upcoming events. Use ticketweb_search to find venues or ticketweb_event for one event.

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": {
      "id": "<id>"
    },
    "name": "ticketweb_venue"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesRequired. Numeric TicketWeb venue id, e.g. 15005.
pageNoOptional. One-based page of the venue's upcoming events, 1-50. Defaults to 1.

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. First observed

TDQS

A4/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 one behavioral fact ('one page of upcoming events'), signaling pagination, but this largely restates the schema's page parameter and omits auth/rate-limit or scope details. Appropriate for a read-only tool with strong annotation coverage.

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, zero waste, and the capability statement is front-loaded before the alternative-tool routing. Every clause earns its place.

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, return values need not be described, and the two parameters are fully documented in the schema. The description is essentially complete for a read-only detail-fetch tool, with only minor omission of prerequisites (already needing an id).

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%: the id parameter explains 'Numeric TicketWeb venue id, e.g. 15005' and page explains the one-based range 1-50 and default. The description adds no syntax or format detail beyond the schema, so the baseline of 3 is correct.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific verb ('Fetch') plus resource ('TicketWeb venue details and one page of upcoming events'), and it explicitly names the sibling tools it is not (ticketweb_search for finding venues, ticketweb_event for a single event). An agent can differentiate it from the sibling tools without opening any schema.

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

Usage Guidelines4/5

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

It routes the agent to alternatives: use ticketweb_search to find venues (implying this tool needs a known id) and ticketweb_event for a single event. That covers the main selection conditions, though it does not spell out exclusions against other venue tools (e.g., vendor alternatives) or state prerequisites like needing a pre-resolved id.

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