Skip to main content
Glama

Predicthq

by io.github.pipeworx-io
OverviewDiscussionsAdmin

Get Event

get_event
Read-onlyIdempotent

Fetch a single PredictHQ event by its id, returning its title, category, rank, predicted attendance, dates, and location. Example: get_event({ id: "abcDEF123" }).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesThe PredictHQ event id, e.g. "abcDEF123".
_apiKeyNoREQUIRED — your own PredictHQ access token. Pipeworx does not front a key for PredictHQ (14-day trial, then sales contact). Free keyless alternatives for event listings: ticketmaster, seatgeek.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / _apiKey / description
      Previous value: -"Optional — your own PredictHQ access token for your own quota; omit to use the shared Pipeworx platform key."New value: +"REQUIRED — your own PredictHQ access token. Pipeworx does not front a key for PredictHQ (14-day trial, then sales contact). Free keyless alternatives for event listings: ticketmaster, seatgeek."
  2. Changed1 schema field changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "_apiKey": "your-predicthq-api-key",
+    "id": "abcDEF123"
+  }
+]
  3. First observed

TDQS

A4.1/5.0
Behavior3/5

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

Annotations already disclose read-only, idempotent, and non-destructive behavior, lowering the bar. The description adds the return fields, which is useful context, but it does not explain auth requirements or error behavior. It adds some value beyond annotations without being rich.

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?

The description is one sentence with a clear verb and an example. It is concise, front-loaded, and every word adds value.

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?

This is a simple single-event fetch tool with good annotations and full schema coverage. The description lists the returned fields, making it sufficiently complete for an agent to understand the tool's behavior and output.

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% with descriptions for both id and _apiKey. The description includes an example call, but this does not add significant meaning beyond the schema. The baseline 3 is appropriate.

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 fetches a single event by its id, listing specific fields returned. This distinguishes it from sibling tools like search_events and nearby_events, which handle different operations.

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 clearly implies when to use this tool: when you have a specific event id and need its details. It does not explicitly name alternatives or exclusions, but the context is clear enough for a simple lookup tool, so it earns a 4 rather than 5.

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

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