Skip to main content
Glama

Skiddle

by io.github.pipeworx-io
OverviewDiscussionsAdmin

Search Events

search_events
Read-onlyIdempotent

Search UK events (gigs, club nights, festivals, comedy, theatre, exhibitions). Filter by location (latitude+longitude+radius), keyword, category, and date window. Sorted by date or distance.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
toNoLatest event date YYYY-MM-DD.
fromNoEarliest event date YYYY-MM-DD (default: today).
limitNoMax events (1-100, default 20).
orderNoResult ordering (default "date"; "distance" needs lat/long).
offsetNoPagination offset (default 0).
radiusNoSearch radius in miles (default 10, used with lat/long).
keywordNoKeyword to match in event/venue/artist, e.g. "techno", "Adele".
categoryNoCategory code: FEST, LIVE, CLUB, COMEDY, THEATRE, EXHIB, KIDS, BARPUB, LGB, ARTS, FILM, SPORT, DATE. Use the categories tool.
latitudeNoSearch-centre latitude (pair with longitude), e.g. 51.5074 for London.
longitudeNoSearch-centre longitude (pair with latitude), e.g. -0.1278 for London.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "keyword": "techno",
+    "latitude": 51.5074,
+    "limit": 20,
+    "longitude": -0.1278,
+    "radius": 10
+  },
+  {
+    "category": "LIVE",
+    "from": "2024-01-15",
+    "latitude": 53.4808,
+    "limit": 50,
+    "longitude": -2.2426,
+    "order": "distance",
+    "radius": 15,
+    "to": "2024-02-15"
+  }
+]
  2. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false. The description adds behavioral context: results sorted by date or distance, default radius 10 miles, and location-based filtering. No contradictions. With good annotations, the description provides useful additional transparency.

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 concise sentences. The first sentence defines the tool's scope and supported event types. The second lists key filters and sorting. Efficient and 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?

No output schema is present. The description covers filters and sorting, but does not mention pagination (offset/limit) or result structure. Schema fills some gaps, so overall it is quite complete for a search tool with well-documented parameters.

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 baseline is 3. The description groups parameters (location, keyword, category, date window) but does not add meaning beyond the schema descriptions. No new semantic insights are provided.

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 clearly states it searches UK events and lists event types (gigs, club nights, festivals, comedy, theatre, exhibitions). It distinguishes from siblings like 'event' (single event retrieval) and 'categories' (listing categories) by specifying the broad search and filtering capability.

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?

The description implies usage for searching events but does not explicitly state when to use this tool vs alternatives like 'event' for specific event details or 'categories' for category codes. It briefly mentions using the categories tool, but lacks exclusions or decision guidance.

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

All Skiddle 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