Skip to main content
Glama

Edmtrain

by io.github.pipeworx-io

Events

events
Read-onlyIdempotent

Find upcoming electronic/dance events, concerts and festivals for a region. Specify a region either by latitude+longitude (returns events within ~75 miles) or by location_ids. Optionally filter by date window, name, and festivals-only.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoMax events to return (1-200, default 50).
stateNoOptional 2-letter state filter when using lat/long, e.g. "CA".
end_dateNoLatest event date, YYYY-MM-DD.
latitudeNoRegion center latitude (pair with longitude), e.g. 37.77 for SF.
longitudeNoRegion center longitude (pair with latitude), e.g. -122.42 for SF.
event_nameNoFilter by event/festival name keyword.
start_dateNoEarliest event date, YYYY-MM-DD.
location_idsNoComma-separated EDMtrain location ids (from the locations tool). Alternative to lat/long.
festivals_onlyNoIf true, return only festivals.

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed1 schema field changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "latitude": 37.77,
+    "limit": 50,
+    "longitude": -122.42,
+    "state": "CA"
+  },
+  {
+    "end_date": "2024-08-31",
+    "festivals_only": true,
+    "location_ids": "nyc,la",
+    "start_date": "2024-06-01"
+  }
+]
  2. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, etc. The description adds specific behavioral detail: events within ~75 miles when using lat/long. This goes beyond what annotations provide, though it could mention result ordering or default limit behavior.

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, concise and front-loaded. Every sentence adds value: first states core function, second explains region specification and optional filters. No wasted words.

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?

Given 9 optional parameters and no output schema, the description gives a complete overview of input modes and filters. References sibling 'locations' tool for location_ids. Could mention that results are a list of events, but that is implied. Nearly complete.

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 (region specification, date window, name, festivals-only) but does not add significant meaning beyond the schema descriptions and examples. It provides a useful summary but no deep parameter insights.

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 the tool finds upcoming electronic/dance events, concerts, and festivals. It explicitly distinguishes region specification (lat/long vs location_ids) and mentions filtering options, leaving no ambiguity about its purpose.

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?

The description provides clear when-to-use guidance for finding electronic events by region, with two methods of region specification. It does not explicitly mention when not to use (e.g., for past events or other genres), but the context is sufficient for typical use cases.

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

All Edmtrain toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A3.9/5.0
Disambiguation2/5

Several tools have overlapping or near-identical purposes: ask_pipeworx and ask_pipeworx_beta are currently functionally identical, ask_pipeworx_grounded is the same router with an extraction step, and discover_tools vs suggest_questions both serve as 'what can I do here' entry points. The polymarket_* family is more distinct, but the ask_pipeworx/deep_research overlap alone makes tool selection genuinely ambiguous.

Naming Consistency4/5

The vast majority of tools follow lowercase snake_case with recognizable domain prefixes (ask_pipeworx*, polymarket_*, pipeworx_*), which is a decent pattern. However, there are bare-noun tools (events, locations, recall, forget) and mixed verb-first vs noun-first ordering (list_subscriptions vs entity_profile, scan_dependency vs polymarket_edges), so it is not perfectly uniform.

Tool Count2/5

33 tools is well above the comfortable range and feels heavy even for a broad data-research platform. Many tools are narrow variations (five polymarket analysis tools, four ask_pipeworx variants, three memory tools) that could plausibly be consolidated or exposed as parameterized modes rather than separate top-level tools.

Completeness4/5

For the actual domain suggested by the tool names and descriptions—structured data research, entity profiling, claim verification, and prediction-market analysis—the surface is quite complete: lookup, grounded answers, deep research, comparisons, recent-change tracking, subscriptions, memory, and arbitrage/fill-risk analysis are all covered. However, relative to the server name 'Edmtrain', the event-discovery surface is extremely thin (only events and locations), which is a notable mismatch.

Resources